CORS-4315: enable primary IPv6 when infrastructure ipFamily is DualStackIPv6Primary#171
Conversation
…imary For dual-stack IPv6-primary clusters, instances must have a primary IPv6 address on their primary ENI to registery with the IPv6 Target Groups of API and Ingress load balancers.
|
@tthvo: This pull request references CORS-4315 which is a valid jira issue. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/hold This is a preview of the idea to adjust MAPA to react based on the infra status Important: We have not finalized on which direction to go yet (i.e. auto react or explicit MAPA machine field) 👀 |
|
/hold cancel
I am OK with this approach where we look at Infra CR which I think is what you are calling "auto react" vs adding a new field to MAPA. |
|
/assign @nrb |
|
Hi @yunjiang29 want to check with you, will you test this pr? |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nrb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @sunzhaohua2, as the installer dualstack support is in progress, I can verify this PR myself via local testing (for dualstack) and via presubmit (for regression). Later on, Yunfei can test the full feature together. |
|
/verified by @tthvo Machines are assigned primary IPv6 address as expected. |
|
@tthvo: This PR has been marked as verified by DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@tthvo: all tests passed! Full PR test history. Your PR dashboard. 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. |
Description
For dual-stack IPv6-primary clusters, instances must have a primary IPv6 address on their primary ENI to registery with the IPv6 Target Groups of API and Ingress load balancers. See AWS docs
Notes
This assumes that the containing subnet is dual-stack (has both IPv4 and IPv6 CIDRs) since we are requesting an IPv6 address for the instance. The subnets, created by installer/capa, will be dual-stack and will auto-assign an IPv6 address on launch.