Skip to content
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

MongoDB Enhancements to PDB #30621

Open
edrose opened this issue Nov 25, 2024 · 0 comments
Open

MongoDB Enhancements to PDB #30621

edrose opened this issue Nov 25, 2024 · 0 comments
Assignees
Labels

Comments

@edrose
Copy link

edrose commented Nov 25, 2024

Name and Version

bitnami/mongodb 6.3.0

What is the problem this feature will solve?

The notes for the chart state the following:

NOTE: An update takes your MongoDB(®) replicaset offline if the Arbiter is enabled and the number of MongoDB(®) replicas is two. Helm applies updates to the StatefulSets for the MongoDB(®) instance and the Arbiter at the same time so you lose two out of three quorum votes.

This isn't strictly true. Helm does update both at the same time, however Kubernetes disrupts both the cluster and the arbiter at the same time because the pod disruption budgets are configured to allow it to.

What is the feature you are proposing to solve the problem?

Rather than installing separate pdbs for the mongo cluster and the arbiter, install just a single pdb with selector labels that cover both. Kubernetes will then only allow a single pod of the set of three to go offline at once, solving the issue stated in the notes.

What alternatives have you considered?

Currently I've disabled pdb creation in the chart and I've deployed a custom pdb to cover both the replicas and the arbiter.

@github-actions github-actions bot added the triage Triage is needed label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants