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.

11 of 31 words

Best matches first

Cluster
The whole fleet: a set of machines (nodes) run together by one control plane.
Explained at port 1.1 · The Cluster Map →
ClusterIP
The default Service type: a stable address reachable only from inside the cluster.
Explained at port 1.16 · ClusterIP →
Practice cluster
A small cluster on your own machine (for example kind or minikube) where you can break things safely.
CKA
Certified Kubernetes Administrator: a hands-on exam where you solve real tasks in a terminal against live clusters.
Control plane
The harbor office of the cluster: it decides what runs where and keeps the cluster in the state you asked for.
Explained at port 1.1 · The Cluster Map →
Controller
A quartermaster: a loop that watches the cluster, compares it with what you asked for, and fixes the difference.
Explained at port 1.6 · Controllers: the control loop →
etcd
The cluster's logbook: a key-value store that holds the state of every object.
Explained at port 1.3 · etcd: a key-value store →
kube-apiserver
The radio room: every request to the cluster goes through it, and only it reads and writes etcd.
Explained at port 1.5 · kube-apiserver: what happens on kubectl create →
kubectl
The command-line tool you use to talk to a cluster: create, inspect, change and delete its objects.
Explained at port 1.19 · Imperative vs declarative →
Namespace
A named section of the cluster that keeps teams or apps apart.
Explained at port 1.18 · Namespaces →
Node
One machine in the cluster, a ship in the fleet. Your Pods run on nodes.
Explained at port 1.1 · The Cluster Map →