Reimplement K8s Autodiscovery Feature

[Eldiabolo21]

Hey, I just came across this project and its really amazing. I'm always a fan of automation, and the lack thereof has always bothered me in Uptime-Kuma. So this seems like a great tool.

I would deploy it in a K8s Cluster. So my thought was "Does gatus support autodiscovery?" I found #30 which was about improving autodisovery and i was like "yeaah, great!" I then searched for some docs but couldn't find anything until i stumbled across the removal in the changelogs and the removal discussion.

This is really sad, though I understand the reasoning behind it. However I would like to propose to give this feature another try.

I really like homepages implementation of K8s autodisovery based on annotations: https://gethomepage.dev/configs/kubernetes/#automatic-service-d Maybe this could be a good starting point?

My idea is: The config only has my alert-target(s) and through Annotations on Services/Ingress (and maybe even pods/Deployments/RS/STS) I can add them to Gatus and define also which alerting endpoints are used.

Do you think this could be an option?
Unfortunately I'm one of these people who has many great feature ideas but no capabilities to implement them, aka I'm not a software dev.

Either way, thanks for your work!

[TwiN]

At this point, I'm not interested in re-implementing this within Gatus because it just explodes the size of the container image by several folds for something that a very small percentage of users would use.

Instead, what I'd suggest you look at is something like https://github.com/home-operations/gatus-sidecar which can provide something more Kubernetes-friendly.

That being said, in the future, I would like to work on https://github.com/TwiN/gatus-controller and make a dedicated controller for Gatus on Kubernetes, but I don't have enough free time in my life right now, so it will probably be some time until I can commit to gatus-controller.