Kubernetes Core Concepts, Pods, Nodes and Control Plane
KCNA fundamentals start with what Pods, nodes, clusters, namespaces, the API server, scheduler, controllers, kubelet, and etcd each do.
How to study for Kubernetes and Cloud Native Associate
Treat each question as a foundation check: identify the Kubernetes primitive, connect it to the cloud native pattern, then choose the least surprising operational behavior.
Core concepts
Concept 1
Kubernetes records desired state through the API and relies on independent control loops to move observed state toward it.
Exam cue: Ask whether the behavior belongs to the API server, scheduler, a controller, kubelet, etcd, or the runtime.
Concept 2
The control plane makes cluster-wide decisions, while kubelet and the container runtime realize assigned Pods on each Node.
Exam cue: Separate Pod-level container restart from a controller creating an entirely new Pod.
Concept 3
Pods are replaceable workload instances; stable discovery, durable storage, and higher-level controllers live in separate abstractions.
Exam cue: Use spec for desired configuration and status or conditions for observed state.
Risk pitfalls and guardrails
Treating a Pod as a durable machine with a permanent identity or IP address.
Guardrail: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Assuming a Namespace automatically provides network isolation, encryption, or a separate physical cluster.
Guardrail: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Confusing API persistence in etcd with container execution or application data storage.
Guardrail: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Memory anchors
Pod
A Pod is the smallest deployable Kubernetes unit and wraps one or more tightly coupled containers.
Node
A node is a worker machine that runs Pods through kubelet and a container runtime.
Cluster
A cluster combines control plane components and worker nodes into one Kubernetes environment.
Namespace
A namespace scopes names, policies, quotas, and access boundaries inside a cluster.
API Server
The API server is the front door for Kubernetes object requests and validation.
Scheduler
The scheduler assigns unscheduled Pods to suitable nodes based on constraints and available resources.
Controller Manager
Controllers watch desired state and reconcile actual cluster state toward that desired state.
Etcd
etcd stores Kubernetes cluster state and must be protected because it is the source of truth.
Kubelet
Kubelet is the node agent that reconciles assigned PodSpecs through the container runtime.
Reconciliation
Reconciliation repeatedly compares desired and observed state and acts to reduce the difference.
Checkpoint rule
Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.
Knowledge Check (after reading)
Short check-up to confirm understanding of this module.
Check-up Questions
A web application needs two tightly coupled containers that must share one IP address and communicate over localhost. Which Kubernetes unit should contain them?
Which control-plane component exposes the Kubernetes API used by kubectl, controllers, and node components?
Answer all questions to submit.
Next step personalized recommendations
Continue learning
Move forward only after this module is stable.
What is Pass Harbor?
Completely free exam prep for 317 U.S. exams.
- Practice questions
- Flashcards
- Study guides
- Mock exams
- No registration
- No paywall
- Start instantly
“No more expensive exam prep. Quality study tools should be accessible to everyone.”