Deprecation of DeploymentConfig #3685
Assignees
Labels
Milestone
Comments
andrewsignori-aot
changed the title
andrewsignori-aot
added
the
Waiting
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 8, 2025
# Convert Deployment Config to Deployment - SIMS Web ## Resource - [Redhat Guide](https://developers.redhat.com/learning/learn:openshift:replace-deprecated-deploymentconfigs-deployments/resource/resources:convert-deploymentconfig-deployment?mc_cid=1a844df827&mc_eid=f049851a15) - [Kubernetes rollout status command](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/kubectl_rollout_status/#:~:text=Show%20the%20status%20of%20the,continue%20watching%20the%20latest%20revision.)  ## Updates - [x] Converted the `DeploymentConfig` object `sims-web` to `Deployment` - [x] The metadata label `deploymentconfig` is replaced with label `app`. This label is now used as selector. - [x] The `HorizontalPodAutoscaler` is now attached to `Deployment` instead of `DeploymentConfig`. - [x] The `rollout status` command is now executed on deployment.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 14, 2025
# Convert the following DC to Deployments - [x] Queue Consumers - [x] Workers - [x] API - [x] Load Test Gateway
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 17, 2025
…#4256) ## Convert to Deployment - [x] Convert FormIO DC to deployment ## Update fetch old tags script - [x] Updated fetch old tags script to get the deployed version of `image steam` based on deployment instead of DC.  ## Removed the `creationTimestamp` from metadata in form - [x] Removed `creationTimestamp:null` in metadata from formio objects as it is not followed in other configs in our application.
|
All the deployment configs are converted to deployment during this implementation. |
|
Deployment instructions updated to: https://app.zenhub.com/workspaces/student-information-management-system-5fce9df5aa1b45000e937014/issues/zh/276 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is happening?
Plattaform Services Team is upgrading to OCP 4.14 in 2024 Q3. Coming to this new version, the DeploymentConfig object is being deprecated. There is no immediate effect after the upgrade, any existing DeploymentConfig workloads will continue to run, but eventually this feature will be removed in future upgrades. The recommendation is to use Deployment instead of DeploymentConfig.
When?
OCP4.14 upgrade is scheduled for Silver in mid September, Gold and GoldDR in October. After the upgrade, DeploymentConfig objects will be deprecated and you will start to see warning about the use of them. While DeploymentConfigs are still supported, they are not recommended for any new installations. Only security-related and critical issues will be fixed by RedHat. There is no specific timeline on when DeploymentConfig will stop working on OCP yet, but teams should start converting to Deployment now.
Do I need to do anything?
If you are creating new workloads, make sure to use Deployment instead of DeploymentConfig.
If you have existing DeploymentConfig workloads, please follow this RedHat guidance to convert them to Deployment objects.
Technical
web-sims) and follow the conversion guide to establish the path to be applied to all other deployments.The text was updated successfully, but these errors were encountered: