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

Peer addresses #3419

Closed
lavalamp opened this issue Jan 13, 2015 · 2 comments

Comments

@lavalamp
Copy link
Member

commented Jan 13, 2015

Many apps need to know where their peers are, to do some sort of replication or sharding. (hopefully this isn't a duplicate; I did search...)

We have the "endpoints" concept. If we provided easy-to-use plumbing, that could make it easier to use the above sort of app.

Having kubelet stuff them in env variables is not quite right, because the list could change.

So I propose making a little container that watches endpoints, and writes out a config file whenever they change.

It could take the service to watch as an env var. It should optionally write out a file (using the go template language), optionally run a command, optionally send HUP or whatever else seems useful.

People could use this as a sidecar container in their pod, to get their app joining the rest of their cluster.

@augi

This comment has been minimized.

Copy link

commented Jan 21, 2015

Publish changes via etcd could be a good way.

@bgrant0607

This comment has been minimized.

Copy link
Member

commented Jan 21, 2015

This is #1607.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.