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.

Sign up for GitHub

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

Jump to bottom

Propagation of external service IPs to pods #2647

Closed
jeinwag opened this issue Nov 27, 2014 · 5 comments
Closed

Propagation of external service IPs to pods #2647

jeinwag opened this issue Nov 27, 2014 · 5 comments
Assignees
@thockin
Labels
area/downward-api sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@jeinwag
Copy link

jeinwag commented Nov 27, 2014

Currently, internal service IP addresses (portals) are propagated to pods via environment variables (MY_SERVICE_HOST etc).

Should there be a similar mechanism for external portals (which are created by specifying publicIPs in the service spec)?
@thockin thockin self-assigned this Nov 28, 2014
@thockin
Copy link
Member

thockin commented Nov 28, 2014

To where would we propagate them? No point in exposing them to pods, since they already have internal IPs...

@jeinwag
Copy link
Author

jeinwag commented Dec 1, 2014

I was indeed thinking of the pods, since there might be situations where a service needs to know its public IP address.

@bgrant0607 bgrant0607 added area/downward-api sig/network Categorizes an issue or PR as relevant to SIG Network. labels Dec 1, 2014
@bgrant0607
Copy link
Member

This is a special case of #386, and is related to #560.

Making a service IP known to pods targeted by it is most compelling for nominal services (#260), but I could see it being useful for other cases, also.

We've decided that environment variables are not going to be the mechanism for communicating this type of data -- instead we'll use (pseudo) files and/or HTTP.

@bgrant0607
Copy link
Member

Or, we could make the service look like some kind of network alias or somesuch.

@brendandburns brendandburns mentioned this issue Dec 3, 2014
Closed
@brendandburns
Copy link
Contributor

Updated #386 to include a reference to this bug, closing this as a dupe of that issue.

@bgrant0607 bgrant0607 mentioned this issue Jan 23, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thockin thockin

Labels
area/downward-api sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@thockin @brendandburns @bgrant0607 @jeinwag