You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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.
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.
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.
Is there an existing issue for this?
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
The text was updated successfully, but these errors were encountered: