-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.19, 4.20
-
None
-
None
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
DeploymentConfig resource is deprecated and should be replaced with Deployment. Nevertheless glossary section explains DeploymentConfig just as normal. Newbies might think of DeploymentConfig as more convenient than Deployment.
Version-Release number of selected component (if applicable):
4.20, 4.19
How reproducible:
Always.
Steps to Reproduce:
1. Access to the following content. (4.20) https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/overview/getting-started-openshift-common-terms_openshift-editions (4.19) https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/overview/getting-started-openshift-common-terms_openshift-editions 2. Go to "Deployment and DeploymentConfig" part.
Actual results:
You can confirm that DeploymentConfig might be seen as normally supported resource by novice people.
Expected results:
Maybe you should insert warning that inform users that DeploymentConfig is deprecated. You might be able to reuse warning message from the following documentation. https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/building_applications/deployments#what-deployments-are > As of OpenShift Container Platform 4.14, DeploymentConfig objects are deprecated.
Additional info:
DeploymentConfig is deprecated as following documentation says. https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/workloads_apis/deploymentconfig-apps-openshift-io-v1#deploymentconfig-apps-openshift-io-v1 > Deprecated: Use deployments or other means for declarative updates for pods instead.