DeploymentConfig resources are deprecated starting in OCP 4.14. Release notes.

3scale deployment heavily relies on DeploymentConfig objects. All instances need to be migrated to Deployment k8s API.

• DeploymentConfig API must disappear from the operator's dependencies.
• Capabilities given by the DeploymentConfig API not existing in the Deployment API should have replacement
  • PRE, POST lifecycle hook containers will be removed. Maybe move the functionality to Init Containers available in Deployment API?
    • Special attention to the system-app pre and post hook containers. Sync with system team guys is required.
  • Deployment Triggers
  • Imagestreams. It does not seem that IS API is going to be deprecated. Currently DC objects have a reference to a tag from the IS object. Investigate if IS objects can be integrated with deployment objects. Decide whether 3scale still uses ImageStream API or removes it as well.

• Upgrade procedure is needed. Trying to avoid service disruption. When DB deployments are in place, disruption is unavoidable.

• • Proposal: create deployments and when pods from deployment objects are up&runnning, remove deploymentconfigs.
  • Check DB migration. Reuse PV from a deploymentconfig to a deployment.
• Replace status report now based on deploymentconfigs

Even some labels are:

deploymentConfig: system-redis

The sooner the 3scale operator drops deploymentconfigs, the lower risk that a 3scale release with deploymentconfigs makes it to a OCP without DeploymentConfig API. TBH I expect DeploymentConfig API to be deprecated quite a few releases until it is dropped.