-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TechDebt: Replace Deprecated DeploymentConfig With Deployment. #1468
Conversation
Openshift URLs for the PR Deployment: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #1468 +/- ##
==========================================
+ Coverage 45.92% 46.07% +0.15%
==========================================
Files 907 909 +2
Lines 23537 23597 +60
Branches 3492 3504 +12
==========================================
+ Hits 10809 10872 +63
- Misses 12136 12138 +2
+ Partials 592 587 -5 ☔ View full report in Codecov by Sentry. |
38160d5
to
f616821
Compare
Drop triggers section.
1607c45
to
c391687
Compare
… postgres upgrade.
…into np_devops_update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦖
Quality Gate passedIssues Measures |
Links to Jira Tickets
n/a
Description of Changes
DeploymentConfig
is now deprecated in OpenShift. They should still function for now, but are no longer receiving updates, etc.Deployment changes
DeploymentConfig
to useDeployment
triggers
section, as this does not exist inDeployment
RollingUpdate
which is the only oneDeployment
supports, with fewer configurable settings.image
property, which was previously auto-populated by theDeploymentConfig
based on thetriggers
section (I believe).Deployment
specifically, underselector
you have to includematchLabels
Other changes
Testing Notes
OpenShift pipeline works the same as it did before.
The deployments worked in this PR. I also tried making an app change and adding a new migration, just to ensure that they re-deployed correctly, and they did (I reverted those changes afterwards).