Kubernetes Networking Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
=The DNS Service= | =The DNS Service= | ||
Each Kubernetes [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Cluster|cluster]] has an internal DNS service, with a static IP address that is hardcoded into every pod on the cluster. Every new [[Kubernetes_Service_Concepts#Service|Service]] is automatically registered with the cluster's DNS service so cluster components can find services by name. [[Kubernetes_Higher_Level_Pod_Controllers#StatefulSet|StatefulSets]] and the individual pods managed by a StatefulSet are also registered with the DNS service. | Each Kubernetes [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Cluster|cluster]] has an internal DNS service, with a static IP address that is hardcoded into every pod on the cluster. Every new [[Kubernetes_Service_Concepts#Service|Service]] is automatically registered with the cluster's DNS service so cluster components can find services by name. [[Kubernetes_Higher_Level_Pod_Controllers#StatefulSet|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). | |||
Revision as of 21:48, 21 August 2019
Internal
Kube-proxy
Pod Network
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).