You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is really a must-have feature for customers that want to use Kubernetes and want to comply with modern internet standards. It's fine to have a IPv4-only network inside the Kubernetes cluster itself, but we do want the load balancer to be reachable over IPv6. The load balancer could convert IPv6 to IPv4 to send it to the cluster.
Currently we define the IPv4 address ID in spec.loadBalancerIP, but I think we should make that field comma-separated?
Or: introduce a separate annotation, since loadBalancerIP is deprecated either way.
The text was updated successfully, but these errors were encountered: