Deploying External S-TAP with an operator

Use Kubernetes with a computer assisted software engineering (CASE) operator to deploy your External S-TAPs. You can deploy External S-TAP as a stand-alone service, similar to installing and running the External S-TAP from Cloud Pak for Data v 4.0.

Before you begin

Ensure that the cluster meets the minimum requirements for installing External S-TAP. For more information, see External S-TAP requirements. Verify that a cluster administrator completed the following tasks:
  1. The project where you plan to install External S-TAP exists.
  2. Optional but recommended, export the following environment variables:
    Note: Make sure that the CASE_VERSION is correct for your implementation. Run the following command to check the CASE versions:
    >oc ibm-pak list --case-name ibm-estap
* Versions listing for ibm-estap *
CASE         Version    App Version
ibm-estap    1.0.0      1.0.0
ibm-estap    1.0.1      1.0.1
ibm-estap    1.1.0      1.1.0
ibm-estap    1.1.1      1.1.1
ibm-estap    1.1.2      1.1.2

    The following example shows CASE_VERSION=1.1.1. However, make sure to use the version that matches your app version.

    # Set the working directory to use
export WORKDIR=$HOME
# Set the IBM-PAK working directory
export IBMPAK_HOME=$WORKDIR
# Set the name of the CASE
export CASE_NAME=ibm-estap
# Set the version of the CASE
export CASE_VERSION=1.1.1
# Set the namespace of the Cloud Pak for Data instance
export CPD_NAMESPACE=cpd-inst-01
  3. Use the following command to download the CASE:
    pushd $WORKDIR; oc ibm-pak  get $CASE_NAME --version $CASE_VERSION; popd
  4. For environments that use a private container registry, such as air-gapped environments, the External S-TAP software images are mirrored to the private container registry. For more information, see Mirroring images to your private container registry.
  5. The cluster is configured to pull the External S-TAP software images. For more information, see Configuring the cluster to pull images.
  6. The Guardium External S-TAP catalog source exists. For more information, see Creating catalog sources.
  7. The Guardium External S-TAP operator subscription exists. For more information, see Creating operator subscriptions.
If these tasks are not complete, the External S-TAP installation will fail

About this task

After you have completed the previous steps, you can deploy the External S-TAP container. For details about deploying the External S-TAP container, see Enabling the External S-TAP provisioning UI.