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

Add option to disabled PDB entirely within the helm chart or to set maxUnavailable manually #187

Open
cberge908 opened this issue Mar 1, 2024 · 1 comment

Comments

@cberge908
Copy link

Hi,

we're using Yugabyte in a DEV environment with one replica for master and tservers each.
Due to this setting the PDBs are automatically generated with a maxUnavailable setting of 0 for both statefulsets.
Unfortunately this blocks the automatic cluster node updates.

Would it be possible to either:

  1. Add an option to the chart values to enabled/ disabled pod disruption budgets entirely

or

  1. Set the values for the PDBs manually within the values file.

I do understand that this might not be wanted for most situations (where you would have at least 2 replicas for each) but it would be beneficial to have this option for scenarios like ours.

Cheers,
@cberge908

@iSignal
Copy link
Contributor

iSignal commented Mar 1, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants