In this page:

Overview

The DPOD Cloud Agent component allows support for IBM DataPower Gateways deployed in Kubernetes/OpenShift, and includes the following features:

• Automatic discovery of IBM DataPower Gateways as they are deployed, scaled up or scaled down by the DataPower k8s Operator.

• The collected data is stored in a persistent messaging layer until it is processed by DPOD.

• The DPOD Cloud Agent is highly available and can be scaled up or down as required.

Open

It includes the following components:

• Cloud Agent Operator - manages the installation of the Cloud Agent instances and the discovery of the DataPowerService resources in the cluster.

• Cloud Agent Manager - performs auto-discovery of the DataPower Gateway pods, exposes APIs to DPOD to interact with the Cloud Agent the the DataPower Gateways, maintains the topics in the messaging component, sends keepalive messages, etc.

• Cloud Agent Messaging - stores the collected data from the DataPower gateways until it is processed by DPOD.

• Cloud Agent Syslog Ingester - receives Syslog messages from the DataPower Gateways.

• Cloud Agent HTTP Ingester - receives HTTPS messages from the DataPower Gateways, such as WS-M payloads, API-C Analytics offload, etc.

Available Versions

Operator Installation Mode

When installing an operator via OLM, there are two options for the Installation Mode:

• All namespaces on the cluster: AllNamespaces (aka cluster scope)

• A specific namespace on the cluster: OwnNamespace (aka namespace scope)

In AllNamespaces mode, the Operator will use a ClusterRole and ClusterRoleBinding and using that will have cluster-wide scope to manage DataPower Operations Dashboard Cloud Agent resources across all namespaces. In OwnNamespace mode, the operator will use a Role and RoleBinding as its primary access (limited to the namespace it's installed in), with a limited set of ClusterRole permissions (see Cluster-scope permissions).