-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
1
-
2
-
None
-
Installer Sprint 274, Installer Sprint 275, Installer Sprint 276, Installer Sprint 277, Installer Sprint 278, Installer Sprint 279, Installer Sprint 280, Installer Sprint 281, Installer Sprint 282
User Story:
As a (user persona), I want my single-stack IPv6 workloads (i.e. pods) to be able to reach services on the internet, within the same VPC or across VPC over IPv4.
The motivation is that not all services on the internet support IPv6 yet. Can this be optional?
Acceptance Criteria:
Description of criteria:
- Subnets attribute EnableDns64 set to true
- Route tables associated with private subnets should have a route for destination 64:ff9b::/96 forwarded to NAT gateways (in the same AZ).
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- Routes for private subnets: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/4e912b4e4d1f855abf9b5194acaf9f31b5763c57/pkg/cloud/services/network/routetables.go#L402-L426
This requires/does not require a design proposal.
This requires/does not require a feature gate.