Kubernetes Container Probes: Difference between revisions
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
=Container Liveness Check= | =Container Liveness Check= | ||
The result of the container liveness check is used by Kubernetes to know when to restart the container <font color=darkgray>(Not the pod? How about [[#Operation_Atomicity|atomicity]]?)</font> | The result of the container liveness check is used by Kubernetes to know when to restart the container <font color=darkgray>(Not the pod? How about [[Kubernetes_Pod_and_Container_Concepts#Operation_Atomicity|atomicity]]?)</font> | ||
=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. |
Revision as of 23:03, 2 October 2019
External
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.