-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.4] Backport livez/readyz #17128
[3.4] Backport livez/readyz #17128
Conversation
Signed-off-by: Chao Chen <[email protected]>
Add two separate probes, one for liveness and one for readiness. The liveness probe would check that the local individual node is up and running, or else restart the node, while the readiness probe would check that the cluster is ready to serve traffic. This would make etcd health-check fully Kubernetes API complient. Signed-off-by: Siyuan Zhang <[email protected]>
Signed-off-by: Siyuan Zhang <[email protected]>
cc @serathius @ahrtr |
Signed-off-by: Siyuan Zhang <[email protected]>
785c9cc
to
b6ab239
Compare
Overall looks good to me. @siyuanfoundation could you manually run each probe (/health, /livez, /readyz) based on this PR and paste the output? |
I will backport the e2e tests after merging this PR.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@siyuanfoundation Please don't forget to update changelog for both 3.4 and 3.5. |
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
Similar to #17039