-
Notifications
You must be signed in to change notification settings - Fork 508
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
kubernetes-service-endpoints is down #7
Comments
@hkailantzis the cluster roles are probably not applied properly. The Prometheus deployment needs read access to all cluster components to get the metrics. |
thanks for your reply. Well, I used the cluserRole.yaml file from this repo, but not sure what might be the problem. yaml file is applied.[UPDATE]. I removed the blocks with "annotation_prometheus" from the config map yaml file, as shown in the official example page: |
Closing this as the configs are working.. |
Hi |
@phong-ho is the issue resolved? |
@bibinwilson not yet, Can you give me a hint to troubleshoot the configuration ? |
Hi, I just cloned this repo and deployed it into my kubernetes repo and I am also seeing the |
@jbmcfarlin31 please refer #3 (comment) |
@bibinwilson I actually got this to work by changing the image of prometheus to their latest stable one. I went to version |
kubernetes-service-endpoints is down. Connection refused. Using Exposing Prometheus As A Service, e.g. NodePort with the following annotations:
prometheus.io/scrape: 'true'
prometheus.io/path: /
prometheus.io/port: '8080'
Any hint of what might be wrong ? Also pods are not showing in Prometheus. Using 2.2.1 and 2.3.2 version of the Prometheus image shows same results.
Thanks for repo.
The text was updated successfully, but these errors were encountered: