Helm Chart: Add support for only one replica #18577
Open
+1
−1
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.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
Add support for only one replica in the helm chart
Motivation and Context
using
replicas: 1
used to render something like this:Where
{0...0}
is not supported by the minio server. Now extended with the if statement it will render out the following:The line I edited is one big cluster fuck its basically looping over num pools and then creating a range for num replicas. And I added a additional if else statement in the loop saying it should not create a range if start and end are equal and instead just put the digit as is.
How to test this PR?
I used the helm template preview vscode extension to look at the rendered yaml. But any helm template renderer should work fine.
Then play with the
pools:
andreplicas:
amount and ensure it never produces invalid urls such as{0...0}
while still maintaing multi pool support where every url is unique. Here a few examples so you don't have to do it:The default
The case im trying to fix which used to render {0...0}:
Support for multiple pools is still kept:
And support for multi pool and multi node:
Types of changes
Checklist:
commit-id
orPR #
here)