Self-Healing Applications with Docker and Kubernetes
summary
Kubernetes plus Docker plus minikube get used to build an actual self‑healing setup: a Deployment (replicas=1) with liveness and readiness probes (HTTP GET /healthy and /ready, initialDelaySeconds 5) shows concrete behavior — when the container returns 500 on the liveness endpoint three times the kubelet kills it and the declarative desired state causes a recreated pod after three failed probes. The demo runs live: pod deleted or made unhealthy and Kubernetes replaces it automatically.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:17Agenda
- 3:39The Challenge
- 21:53Recap
- 22:21Health
- 26:56Terminal
- 28:41Deployment Object
- 31:06Deployment Demo
- 34:11Application Demo
related talks
21mSelf-Healing Kubernetes
28mThe Magic of Kubernetes Self-Healing Capabilities
38mScaling your applications with Kubernetes and Docker
28mScaling Node.js Applications with Kubernetes and Docker
03h 41mKubernetes Basics - a live tutorial
30mAfterlife tales: Troubleshooting containerized applications
42mLocal Development Techniques with Kubernetes
45mTroubleshooting containerized applications
