Skip to content
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

etcd on the master should only be accessible from localhost #5962

Closed
roberthbailey opened this issue Mar 25, 2015 · 5 comments
Closed

etcd on the master should only be accessible from localhost #5962

roberthbailey opened this issue Mar 25, 2015 · 5 comments
Labels
area/security priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone

Comments

@roberthbailey
Copy link
Contributor

Forked from #129.

Right now it binds to 0.0.0.0.

@roberthbailey roberthbailey added priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Mar 25, 2015
@roberthbailey roberthbailey added this to the v1.0 milestone Mar 25, 2015
@kelseyhightower
Copy link
Contributor

@roberthbailey Is the goal to run a single etcd instance private to the Kubernetes API server?

@zmerlynn
Copy link
Member

Kelsey - Yeah, that's the goal. (This obviously might differ on Core
setups, but you still could imagine having a separate etcd just for
separation of concerns between fleet / k8s.)
On Mar 27, 2015 7:12 AM, "Kelsey Hightower" notifications@github.com
wrote:

@roberthbailey https://github.com/roberthbailey Is the goal to run a
single etcd instance private to the Kubernetes API server?


Reply to this email directly or view it on GitHub
#5962 (comment)
.

@kelseyhightower
Copy link
Contributor

@zmerlynn The more I think about it, I think that is the right thing to do out of the box. If users really want to share etcd clusters, they can make the configuration changes.

@roberthbailey
Copy link
Contributor Author

@ArtfulCoder was this fixed by #6417?

@ArtfulCoder
Copy link
Contributor

yes, PR #6422

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

4 participants