Probes and Self-Healing
Part of the Kubernetes course
A process that has crashed is easy to deal with. It is gone, the operating system noticed, and Kubernetes starts a new one. The hard case is the process that is still running and no longer working: a web server whose database connection pool has deadlocked, a worker stuck in an infinite loop, an application that leaked memory until every request times out. From the outside the process looks alive.
Nothing in the operating system can tell you the difference, because "working" is a question only your application can answer. So Kubernetes asks it. A probe is a small, repeated question the cluster puts to your container, and the container's answer decides what happens next. ...
Want to learn Kubernetes Probes and Self-Healing in a real environment?
Click below, get a fresh Linux box with Kubernetes ready to go, and work through Probes and Self-Healing hands-on with an AI tutor that knows your code.
Start this lessonProbes and Self-HealingWhat you'll learn
- Liveness probe
- Readiness probe
- Startup probe
- Http probe spec
- Restart policy
- What happens on failure
Read this lesson in your language
All lessons in this course
14 lessons- 1What is Kubernetes25 min
- 2Your First Pod30 min
- 3Deployments and ReplicaSets35 min
- 4Services35 min
- 5Probes and Self-Healing35 min
- 6ConfigMaps and Secrets35 min
- 7Volumes and Persistent Storage35 min
- 8Namespaces and Labels25 min
- 9Ingress35 min
- 10Helm Basics35 min
- 11Scaling and HPA30 min
- 12RBAC35 min
- 13Observability30 min
- 14Capstone: Deploy a Stack60 min
