DCA · Question #76
One of several containers in a pod is marked as unhealthy after failing its livenessProbe many times. Is this the action taken by the orchestrator to fix the unhealthy container? Solution: The…
The correct answer is A. Yes. In specific scenarios, an autoscaler might delete an unhealthy pod to alleviate unproductive resource consumption, rather than restarting it to fix.
Question
One of several containers in a pod is marked as unhealthy after failing its livenessProbe many times. Is this the action taken by the orchestrator to fix the unhealthy container? Solution: The controller managing the pod is autoscaled back to delete the unhealthy pod and alleviate load.
Options
- AYes
- BNo
How the community answered
(47 responses)- A94% (44)
- B6% (3)
Why each option
In specific scenarios, an autoscaler might delete an unhealthy pod to alleviate unproductive resource consumption, rather than restarting it to fix.
While a liveness probe primarily leads to container restarts, a Horizontal Pod Autoscaler (HPA), when scaling down, might target an unhealthy pod for deletion if it's consuming resources without contributing to actual workload and can be removed without violating replica counts. This action, by removing an unproductive resource consumer, could be seen as 'alleviating load' in a broader management context.
The primary response to a liveness probe failure is container restart, but in an autoscaling context, an unhealthy pod could be deemed expendable during a scale-down event to optimize resource usage.
Concept tested: Kubernetes autoscaling and unhealthy pod management
Source: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
Topics
Community Discussion
No community discussion yet for this question.