Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upv1.Pod: User \"kubernetes\" cannot list pods at the cluster scope #4081
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Apr 12, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
kongsys commentedApr 12, 2018
•
edited
Proposal
Use case. Why is this important?
prometheus access k8s, get error , prometheus use bearer token file
service-account.name is prometheus not Kubernetes ,and prometheus run in ec2
Nice to have' is not a good use case :)
Bug Report
What did you do?
What did you expect to see?
What did you see instead? Under which circumstances?
Environment
Linux 4.4.53-1.el7.centos.x86_64 x86_64
Prometheus version:
prometheus, version 2.2.1
Alertmanager version:
not yet use Altermanager
Prometheus configuration file: