Kops: Kops does not expose etcd port for Prometheus scraping
1. What kops version are you running? The command kops version, will display
this information. 1.10.0
2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag. 1.10.7
3. What cloud provider are you using? AWS
I set up cluster on AWS with --private flag set to true.
AWS SecurityGroup created by Kops does not expose master port 4001 to nodes. This prevents Prometheus from scraping etcd status.
Is this intended behaviour? Is there a flag I can use to expost the port?
michaelgeorgeattard
All 7 comments
Presumably this is a security measure, opening the port allows any pod in the cluster to make (potentially unauthenticated) etcd client connections and get root access on your cluster.
gordonm
on 4 Oct 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 2 Jan 2019
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 1 Feb 2019
/remove-lifecycle rotten
alexppg
on 1 Feb 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 3 May 2019
/close
michaelgeorgeattard
on 3 May 2019
@michaelgeorgeattard: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
k8s-ci-robot
on 3 May 2019
Related issues
chrislovecnm
路
3Comments
olalonde
路
4Comments
minasys
路
3Comments
owenmorgan
路
3Comments
Caskia
路
3Comments
Most helpful comment
Presumably this is a security measure, opening the port allows any pod in the cluster to make (potentially unauthenticated) etcd client connections and get root access on your cluster.