Kubernetes defines a set of building blocks ("primitives") which collectively provide mechanisms for deploying, maintaining, and scaling applications. The components which make up Kubernetes are designed to be loosely coupled and extensible so that it can meet a wide variety of different workloads. The extensibility is provided in large part by the Kubernetes API, which is used by internal components as well as extensions and containers running on Kubernetes.
The basic scheduling unit in Kubernetes is called a "pod". It adds a higher level of abstraction to containerized components. A pod consists of one or more containers that are guaranteed to be co-located on the host machine and can share resources.[15] Each pod in Kubernetes is assigned a unique (within the cluster) IP address, which allows applications to use ports without the risk of conflict.[16] A pod can define a volume, such as a local disk directory or a network disk, and expose it to the containers in the pod.[17] Pods can be manually managed through the Kubernetes API, or their management can be delegated to a controller."
https://en.wikipedia.org/wiki/Kubernetes
https://kubernetes.io/
https://github.com/kubernetes/kubernetes
Kubernetes clusters for the hobbyist - https://github.com/hobby-kube/guide
No comments:
Post a Comment