Deploying the DPOD Cloud Agent Instance

In order to deploy the DPOD Cloud Agent instance, a CustomResource should be created.

Consider the following minimal example of the CustomResource. The complete API is documented in DpodCloudAgent.

apiVersion: integration.ibm.com/v1beta1
kind: DpodCloudAgent
metadata:
  namespace: integration
  name: dpod-cloud-agent-prod
spec:
  discovery:
    namespaces:
      - datapower-gateways-ns
  license:
    accept: true
    license: L-AUGV-MGWKD9
    use: Production
  manager:
    externalHost: dpod-cloud-agent-manager.apps.mycluster.com
    imagePullSecrets:
    - ibm-entitlement-key
  messaging:
    externalHost: dpod-cloud-agent-messaging.mycluster.com
    imagePullSecrets:
    - ibm-entitlement-key
    storage:
      className: app-storage
  syslogIngester:
    imagePullSecrets:
    - ibm-entitlement-key
  httpIngester:
    imagePullSecrets:
    - ibm-entitlement-key 
  version: 1.0.22.0

Validating the Cloud Agent Instance

Using the OpenShift Console

To validate the CustomResource using the OpenShift Console, use the following steps.

1. Navigate to your OpenShift Console UI.

2. Navigate to Installed Operators and choose IBM DataPower Operations Dashboard Cloud Agent.

3. Click on DpodCloudAgent tab and make sure the new CustomResource is in Running Phase.

Using the OCP CLI (oc)

To validate the CustomResource using the oc CLI, use the following steps.

1. Execute the following command and make sure the new CustomResource is in PHASE Running:

   # oc get DpodCloudAgent <CR name> -n <Cloud Agent namespace>
   oc get DpodCloudAgent dpod-cloud-agent-prod -n dpod-cloud-agent