Loading page...
kubernetes
10 minDeployments are easy to start and hard to trust. Learn how readiness probes, rollout strategies, and traffic shaping keep Kubernetes services stable during real releases.
devops
5 minDesign a release as a controlled change to code, configuration, and data, with explicit health checks and a recovery plan that matches what can actually be reversed.
Q&A
Q&AUDP has no connection handshake and applications may not answer an invalid or empty probe.
Unlike TCP, UDP does not establish a transport connection before sending a datagram. A missing response can mean filtering, packet loss, an invalid request, or an application that does not reply. Use a valid protocol-level health check and capture at sender and receiver when diagnosing the path.
Q&A
Q&AReadiness decides whether traffic reaches a pod, while liveness decides whether the container needs a restart.
Readiness is a traffic signal: if it fails, the pod is removed from service endpoints and users are not routed to it. Liveness is a health check for the process itself: if it fails, Kubernetes restarts the container. A pod can be alive but not ready, and that is often the correct state during startup or dependency warm-up.