In Container Orchestration, what is the purpose of 'self-healing'?

In Container Orchestration, what is the purpose of 'self-healing'?

• A. Automatically fixing or healing containers when they fail
• B. It increases replication automatically
• C. It prevents any container from failing
• D. It simplifies security policies

Answer: (A)

Self-healing in container orchestration means the system automatically detects when a container or pod is unhealthy and repairs itself to keep the application running as intended. By using health checks (liveness and readiness probes) and the control loop, the orchestrator restarts failed containers, replaces unhealthy pods, or reschedules them to healthy nodes so the desired number of replicas remains available. This keeps apps responsive even when failures occur, without manual intervention. It isn’t about preventing all failures or blindly increasing replicas, and it isn’t about security policies—that’s a different capability.

Self-healing in container orchestration means the system automatically detects when a container or pod is unhealthy and repairs itself to keep the application running as intended. By using health checks (liveness and readiness probes) and the control loop, the orchestrator restarts failed containers, replaces unhealthy pods, or reschedules them to healthy nodes so the desired number of replicas remains available. This keeps apps responsive even when failures occur, without manual intervention. It isn’t about preventing all failures or blindly increasing replicas, and it isn’t about security policies—that’s a different capability.