Skip to content
Captain's Academy0
Kubernetes · The fleet

Captain's dictionary

Every word from the ports, in one plain sentence, with the lesson that explains it.

13 of 31 words

Best matches first

Pod
The smallest thing Kubernetes runs: one or more containers that share a network address and storage.
Explained at port 1.10 · Pods →
Container
A packaged app with everything it needs to run. Pods wrap containers.
Explained at port 1.10 · Pods →
crictl
A command-line tool on a node that talks to the runtime through the CRI to list pods and containers.
Explained at port 1.2B · ctr vs nerdctl vs crictl →
kube-proxy
Runs on every node and turns a Service's virtual IP into forwarding rules that reach the pods.
Explained at port 1.9 · kube-proxy →
kubelet
The agent on every node that starts Pods and reports back to the control plane.
Explained at port 1.8 · The kubelet →
Manual scheduling
Placing a Pod on a node yourself by setting its nodeName, skipping the scheduler.
Node
One machine in the cluster, a ship in the fleet. Your Pods run on nodes.
Explained at port 1.1 · The Cluster Map →
ReplicaSet
Keeps a set number of identical Pods running, and replaces any that disappear.
Explained at port 1.12 · ReplicaSets & labels →
Rolling update
Swapping old Pods for new ones a few at a time, so the app stays up during an upgrade.
Explained at port 1.13 · Deployments →
Scheduler
The part of the control plane that picks a node for each new Pod.
Explained at port 1.7 · The scheduler: filter & score →
Service
A steady address in front of a changing group of Pods, so others can always reach them.
Explained at port 1.14 · Services: why pods need an address →
Taint
A mark on a node that keeps Pods away unless they tolerate it.
Toleration
A setting on a Pod that lets it land on a node with a matching taint.