-
Feature
-
Resolution: Done
-
Critical
-
None
We are deprecating DeploymentConfig with Deployment in OpenShift because Deployment is the recommended way to deploy applications. Deployment is a more flexible and powerful resource that allows you to control the deployment of your applications more precisely. DeploymentConfig is a legacy resource that is no longer necessary. We will continue to support DeploymentConfig for a period of time, but we encourage you to migrate to Deployment as soon as possible.
Here are some of the benefits of using Deployment over DeploymentConfig:
- Deployment is more flexible. You can specify the number of replicas to deploy, the image to deploy, and the environment variables to use.
- Deployment is more powerful. You can use Deployment to roll out changes to your applications in a controlled manner.
- Deployment is the recommended way to deploy applications. OpenShift will continue to improve Deployment and make it the best way to deploy applications.
We hope that you will migrate to Deployment as soon as possible. If you have any questions, please contact us.
- relates to
-
OCPCLOUD-1513 Explain API deprecations
- To Do
-
OCPBUGS-3805 DeploymentConfig pre hook execPods do not mirror the tolerations of the DC
- Closed
-
OCPBUGS-13859 Deploy pod of the deployment config is not following the configured node affinity
- Closed
- links to