Skip to content
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.5] Backport livez/readyz #17039

Merged
merged 4 commits into from
Dec 7, 2023

Conversation

siyuanfoundation
Copy link
Contributor

@siyuanfoundation siyuanfoundation commented Nov 27, 2023

chaochn47 and others added 3 commits November 27, 2023 12:52
Signed-off-by: Chao Chen <chaochn@amazon.com>
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 <sizhang@google.com>
Signed-off-by: Siyuan Zhang <sizhang@google.com>
@serathius
Copy link
Member

Should we backport e2e tests too?

@siyuanfoundation
Copy link
Contributor Author

siyuanfoundation commented Nov 28, 2023

In order to backport the e2e test, it would require backporting a lot of the e2e test framework, because existing Failpoint is in a this agent handler which is very hard to reuse. Is that worth the effort? @serathius

@serathius
Copy link
Member

Yes, it requires some effort, but we should not add features without proper e2e test coverage. Please let me know if you need help with backport.

@siyuanfoundation siyuanfoundation marked this pull request as draft December 5, 2023 00:31
@siyuanfoundation siyuanfoundation force-pushed the release-3.5-step2 branch 2 times, most recently from 3404053 to c74cf77 Compare December 5, 2023 05:19
@serathius
Copy link
Member

Note, I didn't mean that we should backport the e2e framework changes, just backport the e2e test.

@siyuanfoundation siyuanfoundation force-pushed the release-3.5-step2 branch 2 times, most recently from 1a7d50b to 118b5ae Compare December 6, 2023 05:50
@serathius
Copy link
Member

Looking at the e2e framework backports I think it would be easier to move it to separate PR so we ensure it's properly reviewed.

@siyuanfoundation
Copy link
Contributor Author

Will backport e2e tests as followup PRs.

@serathius
Copy link
Member

cc @ahrtr

@ahrtr
Copy link
Member

ahrtr commented Dec 6, 2023

Also which PR are you backporting? Please provide a link to the original PR.

Signed-off-by: Siyuan Zhang <sizhang@google.com>
Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks

@serathius serathius merged commit 6f125ce into etcd-io:release-3.5 Dec 7, 2023
15 checks passed
@siyuanfoundation siyuanfoundation deleted the release-3.5-step2 branch December 7, 2023 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants