-
Notifications
You must be signed in to change notification settings - Fork 999
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
Critical operation PDB #2830
Critical operation PDB #2830
Conversation
892fda8
to
ac0634d
Compare
Statefulset *appsv1.StatefulSet | ||
VolumeClaims map[types.UID]*v1.PersistentVolumeClaim | ||
GeneralPodDisruptionBudget *policyv1.PodDisruptionBudget | ||
CriticalOpPodDisruptionBudget *policyv1.PodDisruptionBudget |
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.
why not make it a map, too?
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.
ok probably it would require quite a few more code changes then ... we can also leave it as is
Documentation is still missing. |
c.CriticalOpPodDisruptionBudget = newPdb | ||
|
||
return nil | ||
} |
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.
with a map we would not need so much redundant code
dddcd56
to
a877524
Compare
👍 |
1 similar comment
👍 |
Create the second PDB to cover Pods with a special "critical operation" label set.
This label is going to be assigned to all pg cluster's Pods by the Operator during a PG major version upgrade, by Patroni during a cluster/replica bootstrap. It can also be set manually or by any other automation tool.