Use serviceName to construct endpoint for prepare-downscale #221
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.
Addresses #125.
Relevant Kubernetes documentation here: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#stable-network-id
When constructing the endpoint to call for a pod's
prepare-downscale,rollout-operatorwas assuming the.spec.serviceNameof aStatefulSetwas equal to the.metadata.nameof theStatefulSet. This happens to be true for each ingesterStatefulSetin Mimir's Jsonnet, but is not true for ingesters in Mimir's Helm since it has a single headless ingester service.A community member kindly submitted a fix for this issue in #173, but it never got a response. From inspection I think that implementation missed support for
statefulsets/scale. It also added anotherStatefulSetquery. I implemented these changes from scratch to address these issues and avoid other unnecessary changes.Marking as draft until I validate some more.Validated locally