Installing a custom DataPower image through API Connect Operator

Summary

DataPower development creates firmware images (special builds) from time to time that are not generally available through normal means (such as fix central or the entitled registry). These images include debug builds, special builds (with custom fixes), and early releases of builds before it is GAed. This How-To provides steps to install the DataPower special firmware images by using API Connect (APIC) Operator from the custom registry.

When APIC Gateway subsystem is installed and managed through APIC, the APIC Operator is responsible for controlling the DataPower firmware version and image deployed from the designated registry. During the deployment process, APIC Operator reconciles the GatewayCluster Custom Resource (CR) and creates a DataPowerService CR that is used by DataPower Operator to install its firmware image available in the designated registry. However, when the special DataPower firmware image needs to be installed by using custom registry, the DataPower CR needs to be modified to reflect the "image" tag with its value so that special firmware is used for installation. You should not directly modify the DataPowerService CRs that are created by the APIC Operator, as any modifications you make will be overwritten by the APIC Operator.