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 upMisconfiguration on kubernetes with insecure binding #3971
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
Mar 15, 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.
theonlydoo commentedMar 15, 2018
What did you do?
Trying to run prometheus in a k8s pod to auto scrape pods.
What did you expect to see?
Resolution of my pods
What did you see instead? Under which circumstances?

Environment
System information:
k8s 1.9.1
/usr/bin/kube-apiserver \ --allow-privileged=false \ --apiserver-count=3 \ --enable-swagger-ui=true \ --external-hostname=my_external_hostname \ --insecure-bind-address=1.2.3.4 \ --bind-address=1.2.3.4 \ --advertise-address=1.2.3.4 \ --service-cluster-ip-range=172.18.0.0/16 \ --etcd-servers=http://1.2.3.5:2379,http://1.2.3.6:2379,http://1.2.3.7:2379 \ --logtostderr=false -v=0