...

• 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

...

• externalHost - The external host for accessing the manager from outside the cluster. It is the user’s responsibility to configure this host as a DNS entry that is available to DPOD. You can inspect the generated host in .status.endpoints of the Cloud Agent CR (see also Endpoints).

• externalPort - The external port for accessing the manager from outside the cluster (default for OpenShift is 443, otherwise 30120).

• incomingTrafficMethod - The method of exposing the manager to incoming traffic from outside the cluster. Available options are:

  • Route (default and available for OpenShift only) - the operator will create a Service and a Route resources.

  • NodePort (default for Kubernetes) - the operator will create a NodePort Service resource.

  • Custom - see “Custom Network Configuration” above.

• incomingTrafficPort - The port for exposing the manager to incoming traffic from outside the cluster (when incomingTrafficMethod is NodePort, default is the value of externalPort).

...