-
Notifications
You must be signed in to change notification settings - Fork 68
🐛 add PDB to make sure at least 1 pod is always available during upgrade #2362
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2362 +/- ##
==========================================
+ Coverage 70.50% 74.52% +4.01%
==========================================
Files 93 93
Lines 7300 7300
==========================================
+ Hits 5147 5440 +293
+ Misses 1719 1429 -290
+ Partials 434 431 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| enabled: [] | ||
| disabled: [] | ||
| podDisruptionBudget: | ||
| enabled: true |
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.
[nit]: perhaps would be better to name it create:?
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.
However, all the other options are named enabled
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.
Actually, is there a reason for this option, and not just create it based on catalog or operatorController state? (rhetorical question)
| {{- if .Values.options.catalogd.enabled }} | ||
| {{- if .Values.options.catalogd.podDisruptionBudget.enabled }} |
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.
[nit]: perhaps we can combine these two into single if
| @@ -0,0 +1,24 @@ | |||
| {{- if .Values.options.operatorController.enabled }} | |||
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.
same comments as for the other pdb.
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
To address OCPBUGS-62517. Currently, the operator-controller lacks
PodDisruptionBudgetconfiguration. During node drain operations or cluster upgrades, all controller pods can be evictedSimultaneously, causing the operator to report
Available=False, which violates the OpenShift API contract:Add PodDisruptionBudget resources with
minAvailable: 1for both controllers to ensure at least one pod remains available during:Reviewer Checklist
Assisted-by: Claude code