feat(helm): support minAvailable and templated name in podDisruptionBudget #21245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request updates the PodDisruptionBudget configuration in the MinIO Helm chart, improving flexibility by supporting both the
minAvailable
andmaxUnavailable
settings.It also update the
metadata.name
field to use a templated value.The name field could be a breaking change. If we prefer to keep the hardcoded value, I can revert the change.
However, I thought it would be better to align with the other manifests.
maxUnavailable
setting was previously hardcoded with the value '1'. Now, if the value is not explicitly set, it will no longer be applied. This change should also be considered a potential breaking change.Motivation and Context
How to test this PR?
helm template minio . --set podDisruptionBudget.enabled=true
helm template minio . \ --set podDisruptionBudget.enabled=true \ --set podDisruptionBudget.maxUnavailable=2 \ --set podDisruptionBudget.minAvailable=1
Types of changes
Checklist:
commit-id
orPR #
here)