The IPv4/IPv6 dual stack in Kubernetes:

Kubernetes' dual-stack networking feature enables the allocation of both IPv4 and IPv6 addresses to Pods and Services. This allows a single Service to be exposed via both an IPv4 address and an IPv6 address simultaneously. When a Service is configured as dual-stack, its clusterIPs and ipFamilies fields will contain entries for both address families. This allows clients to connect to the Service using either protocol, without any translation, as the networking stack natively supports both.

A. Dual-stack provides native support for both protocols; it does not perform translation between IPv4 and IPv6, which is a function of mechanisms like NAT64.
B. Dual-stack assigns separate and distinct IPv4 and IPv6 addresses to a resource; one address is not an alias or a way to access the other.
C. NetworkPolicies are used for securing traffic flow and are not a prerequisite for enabling or using dual-stack networking functionality.

1. Kubernetes Documentation, "IPv4/IPv6 dual-stack". In: Concepts > Services, Load Balancing, and Networking. The documentation states, "You can create Services which can use IPv4, IPv6, or both... Kubernetes allows you to create a dual-stack Service."

2. Kubernetes Documentation, "Services". In: Concepts > Services, Load Balancing, and Networking. The section on "Dual-stack Services" explains that you can set the ipFamilyPolicy to PreferDualStack or RequireDualStack to expose a Service on both IP families.

3. Contino, M., et al. (2021). An analysis of IPv6 support in the Kubernetes ecosystem. 2021 IEEE 22nd International Conference on High Performance Switching and Routing (HPSR). pp. 1-6. DOI: 10.1109/HPSR52026.2021.9481839. This paper discusses the implementation and states that dual-stack allows Services to have both IPv4 and IPv6 ClusterIPs.