Bug 1278240
Summary: | openshift doesn't wait for readiness check to succeed before attempting a liveness check | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Erik M Jacobs <ejacobs> |
Component: | Node | Assignee: | Paul Weil <pweil> |
Status: | CLOSED NOTABUG | QA Contact: | Jianwei Hou <jhou> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-05 03:46:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Erik M Jacobs
2015-11-05 03:24:54 UTC
Liveness and readiness are two independent probes that control different things. Liveness indicates that the container is running. A failure of a liveness probe is an indication that the container is unhealthy and needs restarted. If the liveness probe fails the kubelet will kill the container and restart it. Readiness indicates that the container is ready to receive traffic. When a pod is ready it is added to the endpoints of any service that is selecting the pod. kube docs: https://github.com/kubernetes/kubernetes/blob/b9cfab87e33ea649bdd13a1bd243c502d76e5d22/docs/user-guide/pod-states.md#container-probes |