Customizing a DataPower deployment

Update the GatewayCluster CR to configure DataPowerService APIs to customize your DataPower deployment.

You can set the following properties in the CR. Note that each GatewayCluster CR property has a corresponding DataPowerService API. Refer to the DataPower Operator documentation link for each property:

Note: If you are using a top-level CR (APIConnectCluster), ensure that the spec.gateway section is included. If it is missing, add the spec.gateway section first before adding the required property within it.

Table 1. Mapping of `GatewayCluster` properties to `DataPowerService` properties
GatewayCluster property	DataPowerService property	DataPowerService API Docs
`additionalDomainConfig`	`domains`	domains For domain configuration, see also: Guides: Domain Configuration Features: Configuration Management
`additionalExtraExe`	`extraExe`	extraExe
`additionalInitCmds`	`initCmds`	initCmds
`lifecycle`	`lifecycle`	lifecycle
`healthcheck`	`healthcheck`	healthcheck
`readinessTimeoutSeconds`	`readinessTimeoutSeconds`	readinessTimeoutSeconds
`hostAliases`	`hostAliases`	hostAliases

Examples of how to add the DataPower service properties to a GatewayCluster CR, in an API Connect deployment on native Kubernetes:

Adding additionalDomainConfig:

spec:
  additionalDomainConfig:
  - name: "default"
    certs:
    - certType: "usrcerts"
      secret: "default-cert"
    - certType: "sharedcerts"
      secret: "shared-cert"
    dpApp:
      config:
      - "default-config"
      local:
      - "default-local"

Extending the apiconnect domain:

spec:
  additionalDomainConfig:
  - name: "apiconnect"
    dpApp:
      config:
      - "custom-apiconnect-config"
      local:
      - "custom-apiconnect-local"