The Shrine Archive: Kubernetes Fundamentals for New Followers

A foundational warning

Kubernetes fundamentals are often taught as nouns. The Order teaches them as behaviors. A pod is not an icon. A deployment is not a promise. A service is not a network cable.

Your early competence comes from understanding which part of the system is authoritative, which parts are eventually consistent, and which failures are expected rather than exceptional.

Cluster, node, pod: the physical layer and the fiction layer

A cluster is a set of machines under a shared control plane. Nodes execute; the control plane governs. Pods are the smallest scheduling unit, not a durability boundary.

Kubelet behavior matters: image pulls, eviction under pressure, probe execution, and graceful termination are where workloads either tell the truth or lie.

• Pods are disposable by design; durability lives above them.
• Nodes are failure domains; treat node pressure as a first-class signal.
• Readiness is a contract with traffic; liveness is a contract with restarts.

Deployment and reconciliation

A Deployment is a controller-driven desired state. It expresses how many replicas you want, how updates proceed, and how history is retained.

The operator’s discipline is to understand why reconciliation can stall: admission failures, image pull errors, scheduling constraints, or probes that never become ready.

kubectl get deploy,rs,pods -n <ns>
kubectl describe deploy/<name> -n <ns>
kubectl get events -n <ns> --sort-by=.lastTimestamp | tail -n 30

Service, ingress, and trust boundaries

Services provide stable identity and load balancing over ephemeral pods. Ingress and gateways define border policy: routing, TLS termination, and exposure.

The Order’s framing: networking is governance. If you cannot explain who can talk to whom, you cannot bound blast radius.

• Service selectors are a form of policy: label hygiene matters.
• Ingress is exposure; treat it like a risk decision with audit trails.
• NetworkPolicy enforcement is CNI-dependent; test, don’t assume.

Suggested path through the shrine

Fundamentals are a map. The archive is the territory. Begin with the Primer, then read the Tenets, then enter deeper discipline pages as your questions sharpen.

• Start: Kubernetes Primer → Five Tenets.
• Then: Control planes → Reconciliation → Scheduling → Network boundaries → Observability.
• Return: Operations Handbook when you can name your failure modes.