Add a dual stack configuration example#1356
Conversation
Provides an example CCM daemonset based on the original that enables dual stack networking. Signed-off-by: Nolan Brubaker <nolan@nbrubaker.com>
|
[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 |
|
This issue is currently awaiting triage. If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the The 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. |
Signed-off-by: Nolan Brubaker <nolan@nbrubaker.com>
|
/test pull-cloud-provider-aws-e2e-kubetest2-quick |
|
@nrb: 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 documentation
What this PR does / why we need it:
This PR adds an example DaemonSet and cloud-config file for enabling IPv4 and IPv6 node IPs.
This change was made because kubernetes-sigs/provider-aws-test-infra#530 relies on it - see https://github.com/kubernetes-sigs/provider-aws-test-infra/blob/main/kubetest2-ec2/config/run-post-install.sh#L25 where the examples directory is downloaded. Without these CCM options, nodes in a dual-stack install cannot come online.
This is also useful information for any user looking to use dual stack nodes in general, however.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: