liveBook · Manning

Self-healing mechanism

As explained in Google Anthos in Action

Self-healing is the automatic detection and recovery from defined failures or unhealthy operating conditions.

A self-healing mechanism automatically detects defined failures or unhealthy operating conditions and performs recovery actions. In a container platform, it supports high-availability services by using Kubernetes-native liveness and readiness checks together with workload rescheduling. section 16.1

A self-healing deployment typically provides:

  • Health checks that distinguish whether a service is alive and whether it is ready to receive work. section 16.1
  • Automated recovery for common failures, including rescheduling workloads onto better operating nodes. section 16.1
  • Declarative infrastructure and programmatic rollout, allowing recovery behavior to be managed as part of the platform. section 15.1

How Google Anthos in Action covers it

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.
How it connects
Connects self-healing with Kubernetes, containers, liveness checks, readiness checks, rescheduling, declarative APIs, and high availability.

Also explained in

Compare how 3 books explain self-healing mechanism →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.