In Kubernetes Deployment, you can specify the number of copies of a specific pod. When the number of pods in the entire cluster is less than a thousand copies, kBs will automatically create the…

Question

Options

• ATRUE
• BFALSE

• A
  85% (23)
• B
  15% (4)

Explanation

Option A is correct because Kubernetes Deployments work through a control loop: you declare a desired replica count in the Deployment spec, and the underlying ReplicaSet controller continuously compares the actual number of running pods against that desired number. Whenever the actual count falls below the desired count - due to node failure, manual deletion, or any other cause - the controller automatically schedules new pods to restore the desired state. Option B is incorrect because Kubernetes does not require manual intervention to recreate missing pods; self-healing through automatic reconciliation is a core guarantee of the Deployment controller.

Memory tip: Think of a Deployment's replica count as a thermostat setting. Just as a thermostat kicks in whenever the temperature drops below the set point, Kubernetes kicks in whenever the pod count drops below the specified replicas, always working to restore the desired state.

No community discussion yet for this question.