-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support for multiple k8s clusters #95
Comments
Oh, I was just browsing through the issues and saw this one. |
I run about 18 K8s clusters, and would love to use Icinga-k8s in order to implement the monitoring (using these: https://github.com/redhat-cop/rhdp-monitoring-scripts/tree/main/openshift/ mostly) Right now I have custom scripts reaching out from Icinga to each cluster, but having a full-and-proper monitoring solution for each cluster would make my life infinitely easier from a monitoring perspective. |
I also got Issues running icinga-kubernetes to monitor a cluster. |
Do you try V0.2 Had the same Issues with v0.1. I would also like multi Cluster Support ! PUSH ! |
So far the initial service looks very interesting and I'm tinkering with it a bit.
However, I think most users are going to wind up needing to monitor multiple clusters - a dev one, a test one, and probably 2 production clusters. I can't figure out how this can currently work with it - since it needs a specific KUBERNETES_MASTER env var defined to operate.
My guess is that this would also need some changes to the SQL schema, potentially to support with potentially multiple agents running on different nodes polling different clusters - but updating the same backend DB.
The text was updated successfully, but these errors were encountered: