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

[feat]: add liveness probe #353

Closed
JasonHe-WQ opened this issue Jun 14, 2024 · 0 comments · Fixed by #354
Closed

[feat]: add liveness probe #353

JasonHe-WQ opened this issue Jun 14, 2024 · 0 comments · Fixed by #354

Comments

@JasonHe-WQ
Copy link
Contributor

JasonHe-WQ commented Jun 14, 2024

1. Issue or feature description

Leader election is critical for high availability for production environment. However, the extender does not need leader election, when it goes down, a new leader will take place since liveness probe works.

2. Steps to reproduce the issue

In case the single HAMi scheduler were not healthy or restarting, the total cluster would not schedule any pod since the scheduler is using extender with Bind and the Bind stage is only suitable for one implement. The scheduler itself can be HA, so this issue will focus on liveness probe on deployment of the HAMi scheduler.

3. Information to attach (optional if deemed irrelevant)

Reference: By Tencent Cloud

@JasonHe-WQ JasonHe-WQ changed the title [feat]: add leader election for [feat]: add leader election Jun 14, 2024
@JasonHe-WQ JasonHe-WQ changed the title [feat]: add leader election [feat]: add liveness probe Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant