-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17
-
None
-
None
-
False
-
Description of problem:
In 4.14, deployment configs were deprecated
In the How to plan your environment according to application requirements template it shows that there is a deploymentconfig template which is no longer supported and the template does not create the deployment
I do not know if there is an exact updated template that does the same thing. But I can work on creating one
Version-Release number of selected component (if applicable):
4.17, 4.16, 4.15, 4.14
How reproducible:
100%
Steps to Reproduce:
1. https://docs.openshift.com/container-platform/4.17/scalability_and_performance/planning-your-environment-according-to-object-maximums.html#how-to-plan-according-to-application-requirements_object-limits
2. Scroll to the section showing the deploymentconfig template
3. Deployment config is not a proper template as it was deprecated in 4.14
Actual results:
Services of the template get created, deploymentconfig does not get created because it was deprecated
Expected results:
Be able to properly create the objects defined in the examples.
Additional info:
On the deploymentconfig openshift tab it reads:
Info alert:DeploymentConfig is being deprecated with OpenShift 4.14Feature development of DeploymentConfigs will be deprecated in OpenShift Container Platform 4.14.DeploymentConfigs will continue to be supported for security and critical fixes, but you should migrate to Deployments wherever it is possible.
