Kubernetes Concepts
External
Internal
TODO
Deplete Kubernetes Concepts TO DEPLETE.
Overview
Kubernetes is a container orchestrator. To understand how it works is to understand a set of high level concepts, briefly mentioned here. More details on individual concepts are available on their respective pages. All interactions with a Kubernetes cluster are performed by sending REST requests into an API server. The API server is responsible with managing and exposing the state of the cluster. The cluster consists in a set of nodes. Nodes are used to run pods - pods are scheduled to nodes and monitored closely by the cluster. A pod is the atomic unit of deployment in Kubernetes, and contains one or more containers. Pods come and go - if one pod dies, it is not revived, but another pod might be scheduled as replacement. In consequence, the IP address of an individual pod cannot be relied on. To provide a stable access point to a set of equivalent pods - which is how applications are deployed on Kubernetes, Kubernetes uses the concept of service. A service's IP address and port can be relied on to be stable for the life of the service. All live pods represented by a service at a moment in time are known as the service's endpoint. The association between services and pods they server is loose,