Provisioning nodes with dual-stack enabled will make it easier to export public services as IPv4 address scarcity and costs can be avoided. In Equinix Metal, IP Reservation requests are not guaranteed to return instantly. With a LoadBalancer request scoped to IPv6, these problems can be avoided. Dual Stacking IPv4 and IPv6 makes sense because Equinix Metal provides an IPv4 address for every node.
This issue may be blocked by kube-vip or cloud-provider-equinix-metal feature limitations. If so we should create issues on those projects and link back here.
https://v1-20.docs.kubernetes.io/docs/concepts/services-networking/dual-stack/
Provisioning nodes with dual-stack enabled will make it easier to export public services as IPv4 address scarcity and costs can be avoided. In Equinix Metal, IP Reservation requests are not guaranteed to return instantly. With a LoadBalancer request scoped to IPv6, these problems can be avoided. Dual Stacking IPv4 and IPv6 makes sense because Equinix Metal provides an IPv4 address for every node.
This issue may be blocked by kube-vip or cloud-provider-equinix-metal feature limitations. If so we should create issues on those projects and link back here.