Kubernetes Liveness Probe Explained #kubernetes
Key Takeaways
Kubernetes Liveness Probe is explained in detail, including its purpose, types, and key parameters, with a focus on HTTP, TCP, and exec probes, and how they are used to check if a container is running properly and restart it if necessary
Full Transcript
Liveness probe in Kubernetes is used to check if a container is still running properly. If the probe fails continuously, Kubernetes kills the container and restarts it according to the pod's restart policy. This is useful when a container is alive but stuck or unresponsive. There are three types of liveness probes. One, HTTP, sends an HTTP request to a specified endpoint. Two, TCP, tries to open a TCP connection on a port. Three, exec, runs a command inside the container. Key parameters of liveness probe includes initial delay seconds, which means wait time before the first check. Period seconds, which means how often to check. Failure threshold, which means how many failures before restarting. Here's an example. This probe checks {slash} health every 10 seconds after a 5-second delay. If it fails too many times, the container restarts.
Original Description
This video explains what liveness probe in Kubernetes is in details and simple language with proper visualisation.
#devops
#kubernetes
#k8s
#devsecops
More on: Kubernetes
View skill →Related Reads
📰
📰
📰
📰
Why Restrict PATH in Linux
Medium · DevOps
Before You Sync: Review What Changed in Your Dotfiles
Medium · Programming
Playwright Chronicles: Crafting Elegant Automation in JS/TS from Scratch — Part 53: Connecting…
Medium · DevOps
When OPA’s `semver.is_valid` Runs on What SemVer Rejects
Medium · DevOps
🎓
Tutor Explanation
DeepCamp AI