-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
5
-
None
-
None
-
CLOUD Sprint 279, CLOUD Sprint 280
User Story
As a user I want to configure my nodes to support IPv6 so that I can eventually deprecate IPv4 traffic.
Background
OCPCLOUD-3215 will implement configuration allowing IPv4 and IPv6 traffic to reach the incoming side of a network load balancer. Users must also be able to inform the CCM that they would like their nodes to listen on IPv6 traffic by configuring IPv6 target group listeners.
Steps
- Add support for the annotation service.beta.kubernetes.io/target-group-ip-address-type to the network load balancer implementation.
-
- Valid values are "ipv4" (default) and "ipv6"
- IPv6 must only be allowed when service.beta.kubernetes.io/aws-load-balancer-ip-address-type is set, otherwise assume IPv4.
- Default upstream will be IPv4, however the Openshift Installer will use this to set nodes to IPv6 in dual stack deployments.
- Ignore this annotation if the Service.spec.loadBalancerClass field is set.
Stakeholders
- <Who is interested in this/where did they request this>
Definition of Done
- An IPv6 target group for nodes can be created and attached to a dual stack network load balancer automatically.
- Docs
- Document the {{service.beta.kubernetes.io/target-group-ip-address-type }}annotation and valid values
- Testing
- Ensure that IPv6 traffic can flow into a dual network load balancer and that target nodes are configured with IPv6 as well.
- depends on
-
OCPCLOUD-3215 Support dualstack network load balancers with AWS CCM
-
- To Do
-
-
CORS-4089 Allow running EC2 instances with a primary IPv6 associated with ENI
-
- Code Review
-
- relates to
-
OCPCLOUD-3067 CCM dual stack support on AWS
-
- In Progress
-