✨ feat: add support for controlplane egress mode#6063
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
86b84d0 to
d6c90a5
Compare
Add support for specifying the mode for the control plane egress traffic. The default is to let AWS manage this. It can be changed to "customer routed" which gives greater control to the routing at the cost of you having to manage the routing. Signed-off-by: Richard Case <richard.case@omniva.com>
d6c90a5 to
39871ac
Compare
|
/test pull-cluster-api-provider-aws-e2e-blocking |
|
@richardcase: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add support for specifying the mode for the control plane egress traffic. The default is to let AWS manage this. It can be changed to "customer routed" which gives greater control to the routing at the cost of you having to manage the routing.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
AI Usage:
None
Checklist:
Release note: