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

[Enhancement]: Enhance the check health api to support additional cluster health states #36567

Open
1 task done
huanghaoyuanhhy opened this issue Sep 27, 2024 · 4 comments
Open
1 task done
Labels
kind/enhancement Issues or changes related to enhancement stale indicates no udpates for 30 days

Comments

@huanghaoyuanhhy
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to be added?

In the current check health API, the response only includes a boolean IsHealthy flag to indicate whether the cluster is functioning normally.
However, in practice, the cluster might be in a "sub-healthy" state, where some components are not working properly, but the overall cluster usage is not yet affected. The existing check health API does not effectively reflect this state.

Perhaps we could consider implementing a system similar to Elasticsearch's Cluster Health API, where cluster health is categorized into three states: red, yellow, and green.

Why is this needed?

No response

Anything else?

No response

@huanghaoyuanhhy huanghaoyuanhhy added the kind/enhancement Issues or changes related to enhancement label Sep 27, 2024
@huanghaoyuanhhy huanghaoyuanhhy changed the title [Enhancement]: Enhance the Check Health API to Support Additional Cluster Health States [Enhancement]: Enhance the check health api to support additional cluster health states Sep 27, 2024
Copy link

stale bot commented Oct 29, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Oct 29, 2024
@stale stale bot closed this as completed Nov 9, 2024
@huanghaoyuanhhy
Copy link
Contributor Author

/reopen

@sre-ci-robot sre-ci-robot reopened this Nov 29, 2024
@sre-ci-robot
Copy link
Contributor

@huanghaoyuanhhy: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@stale stale bot removed the stale indicates no udpates for 30 days label Nov 29, 2024
Copy link

stale bot commented Dec 30, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Issues or changes related to enhancement stale indicates no udpates for 30 days
Projects
None yet
Development

No branches or pull requests

2 participants