The Kubernetes reconciliation loop
WHAT IT TESTS: the declarative control loop pattern. OUTLINE: a controller continuously observes actual state, compares to desired state in the spec, and acts to close the gap, level-triggered not edge-triggered.
WHAT IT TESTS: whether you understand Kubernetes' declarative, self-healing core. ANSWER OUTLINE: a controller runs an endless loop that observes the current state, compares it to the desired state declared in the object's spec, and takes corrective action to converge them. It is level-triggered, reacting to the gap itself rather than to one-off events, so it continually corrects drift. The ReplicaSet controller counts matching Pods and creates or deletes Pods until the count equals the desired replicas.
Read the original → interview
- #kubernetes
- #controllers
- #reconciliation
- #replicaset
- #declarative
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.