Kubernetes Container Probes: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
=Container Readiness Check= | =Container Readiness Check= | ||
The result of the container readiness check is used by Kubernetes to know when the container is ready to accept traffic. The pod is considered ready wen all of its containers are ready. The readiness check is used by [[Kubernetes_Service_Concepts#Connecting_Pods_to_Services|services]] to decide whether to send traffic into the pod or not. | The result of the container readiness check is used by Kubernetes to know when the container is ready to accept traffic. The pod is considered ready wen all of its containers are ready. The readiness check is used by [[Kubernetes_Service_Concepts#Connecting_Pods_to_Services|services]] to decide whether to send traffic into the pod or not. Container will be removed from service endpoints if the probe fails. | ||
Revision as of 23:05, 2 October 2019
External
- https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes
- https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
Internal
Overview
Container Liveness Check
The result of the container liveness check is used by Kubernetes to know when to restart the container (Not the pod? How about atomicity?)
Container Readiness Check
The result of the container readiness check is used by Kubernetes to know when the container is ready to accept traffic. The pod is considered ready wen all of its containers are ready. The readiness check is used by services to decide whether to send traffic into the pod or not. Container will be removed from service endpoints if the probe fails.