Open bravinash82 opened 4 years ago
@jezogwza is working on this and will post a WIP soon
@jezogwza should we move this to Treasuremap or would dual stack be something that we enable out of the box in AS2.0? Also think you were going to add some more info here on what actually needs to be done based on lab learnings. https://github.com/airshipit/treasuremap/issues/22 exists for the Calico dual stack settings. This issue is for the k8s components settings. Realize this may just be the "here's how it currently works" given k8s dual stack support is still alpha.
@jezogwza what do we want to do with this issue? Close it? Refer it to Treasuremap?
Did this downstream at some point last yer. We simply need to move this to treasuremap. However, this is not urgent since valid dual-stack is not beta until k8s 1.22 I think.
Problem description (if applicable) Currently there is no mention of inclusion of IPv6 addressing for K8s service network, pod network and for each host interface in the target cluster. Though the interfaces required by hosts is dependent on the cluster design, it is necessary for Airship to specify the framework to include the IPv6 addressing alongside IPv4 addressing.
Proposed change Complete framework for defining and maintaining Dual Stack IP addressing for K8s service network, pod network and for each host interface in both ephemeral and target cluster.
Potential impacts Already defined network security polices for for each application must be augmented with IPv6 policies as well