dataPowerMonitor

Description

The DataPower Monitor spec defines the configuration for the DataPower Monitor Deployment. The DataPower Monitor serves a vital purpose in logging the lifecycle events of DataPower Pods and, optionally, clearing out stale peers in APIC gateway deployments.

Optional parameters:

  • image
  • lifecycleDebounceMs
  • peeringRecoveryCheckIntervalMs
  • monitorGatewayPeering
  • livenessProbePort
  • resources
  • xmlMgmtPort
  • env

Parameters

image

This optional property sets the image for the monitor Deployment.

Defaults to docker.io/ibmcom/datapower-monitor:latest.

lifecycleDebounceMs

This optional property sets the minimum time between logged lifecycle events.

Defaults to 10000.

peeringRecoveryCheckIntervalMs

This optional property sets the interval in which the Monitor will scan for stale peers.

Defaults to 1000.

monitorGatewayPeering

This optional property turns the peering management feature on and off.

Defaults to false.

livenessProbePort

This optional property sets the port for the liveness probe.

Defaults to 8080.

resources

This optional property configures the resources for the DataPower Monitor Pod.

Defaults to:

requests:
  cpu: 250m
  memory: 256Mi
limits:
  cpu: 500m
  memory: 1Gi

xmlMgmtPort

This optional property configures the port used to connect to the DataPower XML Management Interface. This value should match the port the xml-mgmt object in the DataPower default domain is configured to listen on.

Defaults to 5550.

env

This optional property allows you to set custom environment variables that will be set and used within the DataPower Monitor container. This property exposes the Kubernetes API for declaring environment variables in the container, and thus follows the same schema. For more information, please see the Kubernetes documentation.

Example

apiVersion: datapower.ibm.com/v1beta1
kind: DataPowerService
metadata:
  name: example-dpservice
spec:
  datapowerMonitor:
    image: docker.io/ibmcom/datapower-monitor:latest
    lifecycleDebounceMs: 10000
    peeringRecoveryCheckIntervalMs: 1000
    monitorGatewayPeering: false
    livenessProbePort: 8080
    xmlMgmtPort: 5550
    resources:
      requests:
        cpu: 250m
        memory: 256Mi
      limits:
        cpu: 500m
        memory: 1Gi
    env:
    - name: K8S_DPM_DEBUG
      value: "*"