Kubernetes Networking Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 20: Line 20:
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).
The DNS service is built on [[CoreDNS]].

Revision as of 00:25, 19 October 2019

Internal

TO DO

Kube-proxy

Kube-proxy

Pod Network

Every pod in the Kubernetes cluster has its own IP address, which is routable on the pod network, so every pod on the pod network can talk directly to every other pod.

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.