-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add podDisruptionBudget.enabled value #49
Comments
Totally wild that nobody else has asked for this? Maybe everyone is just creating their own PDB for it like we are? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When draining a Kubernetes node with
kubectl drain
, several couchdb pods are sometimes evicted at the same time, resulting in an unavailable couchdb cluster.Describe the solution you'd like
Adding a
kind: PodDisruptionBudget
option to allow for drain to respect the disruption budget. For example waiting for the first evicted pod to be ready before evicting the next one.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Smaller kubernetes clusters are more affected by this since there are more chances that 2 couchdb pods are scheduled on the same node.
Here is an example of values that this could be controlled with:
The text was updated successfully, but these errors were encountered: