Kubernetes Networking Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
{{Internal|Kubernetes_Control_Plane_and_Data_Plane_Concepts#Kube-proxy|Kube-proxy}} | {{Internal|Kubernetes_Control_Plane_and_Data_Plane_Concepts#Kube-proxy|Kube-proxy}} | ||
=Pod Network= | =Pod Network= | ||
Every pod in the Kubernetes cluster has its [[Kubernetes Pod and Container Concepts#Pod_IP_Address|own IP address]], which is routable on the pod network, so pods can communicate with each other. | |||
=The DNS Service= | =The DNS Service= | ||
Revision as of 23:25, 6 September 2019
Internal
Kube-proxy
Pod Network
Every pod in the Kubernetes cluster has its own IP address, which is routable on the pod network, so pods can communicate with each other.
The DNS Service
Each Kubernetes cluster has an internal DNS service, with a static IP address that is hardcoded into every pod on the cluster. Every new Service is automatically registered with the cluster's DNS service so cluster components can find services by name. StatefulSets and the individual pods managed by a StatefulSet are also registered with the DNS service.
The DNS service is built on CoreDNS (https://coredns.io).