Always enable AWS load balancer controller for clusters with IPv6 #1099
Conversation
This file contains 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
gardener-robot
added
needs/review
gardener-robot-ci-3
added
the
reviewed/ok-to-test
49 tasks
gardener-robot-ci-1
added
needs/ok-to-test
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.
How to categorize this PR?
/area networking
/kind enhancement
/platform aws
What this PR does / why we need it:
Always enable AWS load balancer controller for clusters with IPv6.
AWS cloud controller manager only supports purely IPv4 load balancers. It will not work in IPv6-only environments and does not offer the full functionality in dual-stack environments. Therefore, this change always enabled the fully IPv6-capable AWS load balancer controller in case a shoot cluster with IPv6 is created.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: