fix: switch zone aware *.ingress.cluster.local ClusterIP AZ aware config#11010
Merged
Conversation
…ware without automatic guardrails Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Member
Author
|
@mikkeloscar what do you think of the change? The eks cluster had some hpa e2e error |
Contributor
|
👍 |
Contributor
|
We agreed to disable Tier 1+2 prod initially via CCM so it only gets rolled out to Tier 3+4 via this PR |
Member
Author
|
👍 |
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
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.
fix: switch zone aware *.ingress.cluster.local ClusterIP to be zone aware without automatic guardrails
My assumption is that it either flaps all the time or is enabled all the time. In both cases it would be a fix not a feature.
If it's disable and now enabled it should not matter either because skipper-ingress will handle the load anyways.