Eric Greer

Hey @OmerKahani - we've seen this feature request come through before. What keeps this from being an obvious add is the addition of authentication requirements. Any endpoint of Kuberhealthy that...

Thanks for info. External-secrets looks pretty useful. I will keep that in my toolkit! Revisiting my thoughts here, I agree with @OmerKahani that a UI would be awesome for Kuberhealthy....

This makes sense, and repeatedly polling the API server is not optimal. It seems like Kuberhealthy needs a refactor to a [reflector cache](https://kubernetes.io/docs/reference/using-api/api-concepts/#efficient-detection-of-changes) for `khstate` and `khcheck` resources. Then, when...

I just did some work on this... I am refactoring this to use the existing cache for `khstate` resources... Progress is in the [khstate-cache](https://github.com/kuberhealthy/kuberhealthy/tree/khstate-cache) branch.

Addressed [here](https://github.com/kuberhealthy/kuberhealthy/issues/1015#issuecomment-1040732961)

Not sure this is in scope for the project given that prom has alert management, but I am leaving it open as a proposal.

That sounds really interesting! Many of the checks I see on your GitHub project page seem like they could be used as Kuberhealthy checks. You should be able to integrate...

This also may be related to #880. Kuberhealthy was designed originally to be "okay" with two masters running at the same time in order to avoid having some external source...

I think this is useful information to have displayed. I agree that we would have to append these messages into the details for that check. It could get messy and...

This seems like a helpful idea, but we have some thinking to do about how this behaves when `khjob` states are returned. Also, if we are only going to return...