More flexible ElasticSearch template #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dbackeus
changed the title
dbackeus
changed the title
dbackeus
force-pushed
the
alternative-elasticsearch
branch
3 times, most recently
from
1b02f80 to
1a4f0ef
Compare
p-wall
approved these changes
Nov 5, 2024
| - name: {{ .Chart.Name }}%{suffix} | ||
| nodeSets: | ||
| - name: default | ||
| count: {{ .Values.resources.%{camelName}.replicas }} |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Contributor
Author
|
Note to self: We should add a service that will include all nodesets except the tiebreaker and use that for the recommended |
When just having a single nodeSet with count for replication, we can't control which pod gets decommissioned when scaling down. Using named replicas we can achieve better control for these kinds of use-cases.
dbackeus
force-pushed
the
alternative-elasticsearch
branch
from
1a4f0ef to
701f328
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When just having a single nodeSet with count for replication, we can't control which pod gets decommissioned when scaling down.
Using named replicas we can achieve better control for these kinds of use-cases.