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:
Add an option to the chart values to enabled/ disabled pod disruption budgets entirely
or
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.
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:
or
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