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
- Node
- One machine in the cluster, a ship in the fleet. Your Pods run on nodes.
- Explained at port 1.1 · The Cluster Map →
- NodePort
- A Service type that opens the same port (30000-32767) on every node.
- Explained at port 1.15 · NodePort →
- Cluster
- The whole fleet: a set of machines (nodes) run together by one control plane.
- Explained at port 1.1 · The Cluster Map →
- 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 →
- LoadBalancer
- A Service type that asks your cloud for a load balancer with one public IP, built on a NodePort.
- Explained at port 1.17 · LoadBalancer →
- Manual scheduling
- Placing a Pod on a node yourself by setting its nodeName, skipping the scheduler.
- Scheduler
- The part of the control plane that picks a node for each new Pod.
- Explained at port 1.7 · The scheduler: filter & score →
- 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.