Code Block
oc apply -f ibm-datapower-operations-dashboard-cloud-agent-operator.yaml

IBM DataPower Operations Dashboard Cloud Agent Network Configuration

The Cloud Agent sends and receives data to / from the DataPower Operations Dashboard installed outside OCP .

Currently the DataPower Operations Dashboard Cloud Agent Operator support the following methods for exposing the cloud agent’s services :

NodePort - (default) the Cloud Agent operator will create services with type NodePort to expose services externally to OCP.
Custom - Other methods that the user would like to implement in order to expose the Cloud Agent services (example : ingress controller, LoadBalancer service etc). for more information see Kubernetes documentation
The resources created by the user will not be managed (owned) by the Cloud Agent operator, It is the user responsibility to create, update and delete these resources.

Cloud Agent Inbound (ingress) Communication

The Cloud Agent inbound communication include

Management API invocation generated by DataPower Operations Dashboard to the managercomponent of the Cloud Agent
Kafka communication to the messaging component of the Cloud Agent (messaging brokers).

The messaging component has number of properties (in the Cloud Agent CR) for controlling the communication:

incomingTrafficMethod - The method of exposing the messaging to incoming traffic from outside the cluster. Available options are: Custom, NodePort (default is NodePort)
externalHost - The external host for accessing the messaging from outside the cluster. This value will be published by the messaging brokers (Kafka).
externalPortStart - The starting external port for accessing the messaging from outside the cluster. The bootstrap endpoint will use this port, and each messaging broker will use a consecutive port( default is 30100).
incomingTrafficPortStart - The starting port for exposing the messaging to incoming traffic from outside the cluster (when incomingTrafficMethod is NodePort). The bootstrap endpoint will use this port, and each messaging broker will use a consecutive port. (default is the value of externalPortStart )

For that the Cloud Agent Operator will create the following Kubernetes services:

<CR name>-msg-bse-svc - NodePort services for externally accessing the messaging bootstrap port.
<CR name>-msg-dir-svc-<broker number starting 0> - Messaging broker 0 (zero) service for externally direct access to this broker, will use port externalPortStart +1 (30101, 30102 etc). Each messaging broker will have similar service.

The Manager component has number of properties (in the Cloud Agent CR) for controlling the communication:

incomingTrafficMethod- The method of exposing the messaging to incoming traffic from outside the cluster. Available options are: Custom, NodePort, route(default is Route (OpenShift only) / NodePort)
externalHost - The external host for accessing the manager from outside the cluster.
externalPort- The external port for accessing the manager from outside the cluster (default is 443).
incomingTrafficPort - The port for exposing the manager to incoming traffic from outside the cluster (when incomingTrafficMethod is NodePort). (default is the value of externalPort ).

For that the Cloud Agent Operator will create the following OCP route:

...