Skip to main contentIBM DataPower Operator Documentation

Release Notes

Release notes for CD releases.

1.5.3

  • Add support for DataPower firmware version 10.0.1.7, available in the 10.0-lts channel.
  • Fix an issue preventing DataPower pods from scheduling on Kubernetes when running under the restricted PodSecurityPolicy.
  • Fix an issue in the conversion webhook management which caused errors when more than one namespace-scope operator was installed on a cluster.

1.5.2

  • Add support for DataPower firmware version 10.0.4.0sr1, available in the 10.0-cd channel.
  • Add support for DataPower firmware version 10.0.1.6sr1, available in the 10.0-lts channel.
  • Fix an issue relating to conversion webhook discovery causing unnecessary queries to the Kubernetes API server.
  • Fix an issue which caused status updates of the DataPowerService custom resource to overwrite existing status erroneously.

1.5.1

1.5.0

Enhancements

  • Add support for DataPower firmware version 10.0.4.0, available in the 10.0-cd channel.
  • Add Certificate Manager integration for operator and webhook pods. Note: requires v1.0 cert-manager. For more info, see Certificate Manager.
  • Various improvements to the DataPower Monitor management of gateway-peering configurations to improve upgrade resiliency and overall stability.
  • Add default NetworkPolicies for DataPowerService operand pods.
    • In vanilla Kubernetes, an allow-all Ingress and Egress rule is created.
    • In OpenShift (OCP), an allow-all Ingress is created.
  • Improve validating and mutating (default) webhook behavior by running these webhooks during reconciliation of DataPowerService custom resources.
  • Add container probes to the conversion webhook pod.
  • Various improvements to debug logging for troubleshooting.

Fixes

  • Fix an issue where updating an extraExe ConfigMap does not trigger a rolling update of the DataPower StatefulSet.
  • Fix an issue where the DataPowerService controller would attempt to modify an immutable field on the managed StatefulSet.
  • Fix an issue where the DataPowerMonitor controller could leak an updater instance and continue trying to reconcile a CR which no longer exists.
  • Fix an issue relating to the icp4i-od-store-cred Secret (used by odTracing) which caused unnecessary rolling updates to the StatefulSet.
  • Fix an issue relating to the defaulting of imagePullPolicy which caused unnecessary rolling updates to the StatefulSet.

1.4.3

  • Add support for DataPower firmware version 10.0.1.5, available in the 10.0-lts channel.

1.4.2

  • Add support for DataPower firmware version 10.0.3.0sr, available in the 10.0-cd channel.
  • Fix an issue which caused the StatefulSet to perform a rolling update immediately after becoming Ready.
  • The developers-limited DataPower image is now hosted on IBM Container Registry at icr.io/integration/datapower/datapower-limited.
  • New ibm-datapower-operator CASE, see Installation via CASE for details.
    • The mirror-images action now requires a --groups argument to specify which DataPower images to mirror.

1.4.1

  • Add support for DataPower firmware version 10.0.1.4, available in the 10.0-lts channel.
  • Fix issue related to GID / UID of DataPower pods when running on vanilla Kubernetes.

1.4.0

Starting with this release, all operator images are published to IBM Container Registry (icr.io/cpopen) instead of Dockerhub (docker.io/ibmcom).

DataPowerService v1beta3 API

  • Add support for IBM DataPower Gateway firmware version 10.0.3.0.
  • New property runAsRoot that allows for DataPower containers to be run as root user.
  • New property jaegerTracing for use with external collectors.
  • New property passphraseSecret in the domains spec allows for domain-settings passphrase to be set, for password-alias decryption.
  • New property imagePullPolicy to set the IBM DataPower Gateway container’s image pull policy.

Platform

  • Minimum Kubernetes version is now 1.19.

1.3.1

  • Add support for DataPower firmware version 10.0.1.3, available in the 10.0-lts channel.
  • Fix split-cluster issue related to gateway-peering in API Connect Gateway deployments.

1.3.0

v1beta3 API

This version brings a new v1beta3 version of the DataPowerService CRD, adding the following capabilities:

  • Horizontal and Vertical Pod Autoscaling
  • Kubernetes container lifecycle hooks
  • License acceptance enforcement during upgrade
  • Pause reconciliation for troubleshooting

Upon upgrading to 1.3.0, any v1beta2 DataPowerService instances will automatically be migrated to v1beta3.

Note that only the DataPowerService CRD has updated to v1beta3, the DataPowerMonitor CRD remains at v1beta2.

Enhancements

  • Conversion webhook management will automatically upgrade the conversion webhook runtime when necessary (such as upgrade from 1.2.x to 1.3.x).
  • Stricter validation for minimum CPU and Memory allocations for DataPower containers.

Changes

  • Minimum CPU count for DataPower containers has been lowered to 1.
    • The default CPU request for nonproduction containers is now 1.
    • The default CPU request for production containers remains 4.
  • DataPowerService CPU request (spec.resources.requests.cpu) now supports Kubernetes resource quantity formatting.
    • This means that CPU can be requested using milli-CPU string, such as 4000m for 4 cores.
    • Partial CPU values (such as 2500m are not supported).

Fixes

  • Fix ordering of application domain config initialization during DataPower container startup.

1.1.1

  • Fixes an issue relating to metering and licensing of DataPower Virtual Edition for Nonproduction, when deployed in IBM Cloud Pak for Integration.
  • Fixes an issue relating to the storage.size property rendering in OCP Console UI, as well as IBM Cloud Pak for Integration Platform Navigator.
  • Fixes an issue relating to the name generation and reconciliation of the username-commands ConfigMap created by the operator.
  • Adds documentation links to the ClusterServiceVersion for both CRDs, as well as this documentation website.
  • Conversion webhook management routine will now adopt orphaned webhook deployments if found during reconciliation.

1.1.0

v1beta2 APIs

1.1.0 introduces a new v1beta2 API version, consisting of an updated DataPowerService CustomResourceDefition (CRD), and a new DataPowerMonitor CRD.

For more details on the (automatic) API migration process, see API Migration.

With the new v1beta2 API, the following changes have been made:

DataPowerService

  • Removed dataPowerMonitor (replaced by DataPowerMonitor CRD).
  • Added support for custom tolerations.
  • Added support for custom nodeSelector.
  • Added mgmtPorts to Custom Resource Status.
  • Changed the version channel structure.

DataPowerMonitor

See the API spec here, and more information on the functionality here.

1.0.2

  • Add support for DataPower firmware version 10.0.0.1.
  • Add support for DataPower Monitor version 1.0.1.
  • Add DataPower init script to clean temporary:///config on boot.

1.0.1

  • Several changes and enhancements to support deployment via IBM Cloud Pak for Integration, including:
    • A minimal ServiceAccount is generated for use by the StatefulSet is none is provided in the DataPowerService Custom Resource spec.
    • Support for automatically using an ibm-entitlement-key Secret to pull images from the IBM Container Registry.
    • Labels and Annotations for Licensing and Metering of workloads, both standalone and within IBM Cloud Pak for Integration.
    • Kibana dashboard support.

1.0.0

Initial release.