-
Story
-
Resolution: Done
-
Major
-
None
-
openshift-4.14
-
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.
UX Input: https://docs.google.com/document/d/1FXxHcsC8llE5IEFJmU3RTYDQBP9-dao718pEwAzKGQw/edit
AC: Add alert to DC list, details and create page to notify user that the DC resource is becoming deprecated in favour of Deployment. Alert should also contain link to Deployment docs,
- blocks
-
WRKLDS-754 Deprecate DeploymentConfigs in 4.14
- Closed
- is related to
-
OCPBUGS-17085 Deprecated Alert for DeploymentConfig is missing in Topology -> DC details page
- Verified
- links to