Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

Which is the highest level abstraction in kubernetes?


Asked by Emmaline Romero on Dec 06, 2021 FAQ



Kubernetes’s architecture makes use of various concepts and abstractions. Some of these are variations on existing, familiar notions, but others are specific to Kubernetes. The highest-level Kubernetes abstraction, the cluster, refers to the group of machines running Kubernetes (itself a clustered application) and the containers managed by it.
Additionally,
Kubernetes contains a number of abstractions that represent the state of your system: deployed containerized applications and workloads, their associated network and disk resources, and other information about what your cluster is doing. These abstractions are represented by objects in the Kubernetes API.
And, The levels shaded blue are higher-level K8s abstractions. The green levels represent Nodes and Node subprocess that you should be aware of, but may not touch. Note that your K8s instances will often have multiple Pods that can run on a single Node.
Furthermore,
The Pod is the basic building block of Kubernetes. A Pod contains a group of one or more containers. Generally, each Pod has one container. Pods handle Volumes, Secrets, and configuration for containers. Pods are ephemeral. They are intended to be restarted automatically when they die.
Likewise,
Kubernetes Nodes. The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. The Kubernetes master controls each node; you’ll rarely interact with nodes directly.