Self-healing mechanism
A self-healing mechanism automatically detects failures or deviations from a desired state and takes corrective action to restore or maintain system operation.
Kubernetes in Action, Second Edition
A self-healing system automatically detects or tolerates failures and restores affected workloads or services without requiring immediate manual intervention.
- How it is used
- Uses Kubernetes to maintain application availability while abstracting software recovery and failed-node handling from application code.
- How deep it goes
- Explains automatic restarts and workload relocation for software and hardware failures, but does not detail detection or controller internals.
- Examples
- Uses an application that exhausts memory and a worker node failure requiring application movement.
- What you can do after
- Evaluate/understand how Kubernetes preserves service through automatic application restart and relocation after node failure.
Read how Kubernetes in Action, Second Edition explains self-healing mechanism →
Google Anthos in Action
Self-healing is the automatic detection and recovery from defined failures or unhealthy operating conditions.
- How it is used
- Deploys high-availability services on container platforms so common failures and recovery tasks are handled automatically.
- How deep it goes
- Defines checks and rescheduling as native mechanisms but does not detail probe configuration, failure thresholds, or recovery workflows.
- Examples
- Uses containerized services, workloads moved to better nodes, and legacy applications operated as cloud-native objects.
- What you can do after
- Operate/configure containerized services with native health checks and automated rescheduling for common failure scenarios.
Read how Google Anthos in Action explains self-healing mechanism →
Effective Platform Engineering
Self-healing is the capability of a system to detect deviations from its desired state and automatically restore correct operation.
- How it is used
- Uses platform orchestration to restore desired state automatically and reduce engineering friction.
- How deep it goes
- Explains desired-state correction, Kubernetes actions, telemetry triggers, and limits around unknown failure modes.
- Examples
- Uses failing-service redeployment, workload migration, traffic-based scaling, CPU thresholds, and API capacity limits.
- What you can do after
- Operate/configure Kubernetes-based correction for known violations of healthy service states.
Read how Effective Platform Engineering explains self-healing mechanism →
Related concepts
- Kubernetesincludes · Kubernetes is an open-source platform for orchestrating and automating the deployment, scaling, and management of containerized workloads across computing clusters.
- known knownused by · A known known is a fact or condition whose existence and relevant behavior are recognized and understood.
- container platformuses · A container platform provides infrastructure and tooling for building, deploying, running, networking, and managing isolated software containers.
- health checkuses · A health check is an assessment or probe that determines whether a system, service, or component is functioning acceptably according to defined criteria.
- platform engineeringused by · Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable, self-service capabilities and delivery workflows.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.