4 ms·
Kubernetes isn't IPv4 only. https://kubernetes.io/docs/concepts/services-networking/dual-stack/ https://kubernetes.io/docs/concepts/services-networking/dual...
by raesene9 5y ago
Kubernetes isn't IPv4 only. https://kubernetes.io/docs/concepts/services-networking/dual-stack/ https://kubernetes.io/docs/concepts/services-networking/dual... Dual stack is stable and has been around a while.
Also you don't have to use NAT even with IPv4, it's just that most CNIs implement Kubernetes networking with non-addressable pod addresses. It's perfectly possible to make service and pod addresses routable from outside the cluster.
- motoboi 5y ago> Also you don't have to use NAT even with IPv4, it's just that most CNIs implement Kubernetes networking with non-addressable pod addresses. It's perfectly possible to make service and pod addresses routable from outside the cluster. This is the default on Google Cloud now. Also an option on Azure. At first I found it to be a strange decision, but then I realized the beauty of it, having pod as first class citizens of the cloud.
- bakies 5y agoYes! At home I have the pod IP space routed and can connect to pods with out any port-forwarding.