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

Add KUBERNETES_NAMESPACE variable to Pod containers #6354

Closed
mfojtik opened this issue Apr 2, 2015 · 5 comments
Closed

Add KUBERNETES_NAMESPACE variable to Pod containers #6354

mfojtik opened this issue Apr 2, 2015 · 5 comments
Labels
area/downward-api priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@mfojtik
Copy link
Contributor

mfojtik commented Apr 2, 2015

If you want to make a REST calls from containers running in Pod to KUBERNETES_SERVICE, it would be handy to have the namespace that container is launched in available inside the container.
@mfojtik
Copy link
Contributor Author

mfojtik commented Apr 2, 2015

cc @derekwaynecarr

@bprashanth bprashanth added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Apr 2, 2015
@bgrant0607 bgrant0607 added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. area/downward-api labels Apr 7, 2015
@bgrant0607
Copy link
Member

We want to support passing this information to containers, but not by exposing Kubernetes-specific environment variables.

This is essentially the same issue as #386, #560, parts of #1768, #2316 (comment), #5093, and #6000. The most concrete discussion was in #2316, but the most appropriate issue to use is #386.

@pmorie
Copy link
Member

pmorie commented Apr 11, 2015

@mfojtik I have a WIP that will encompass this; will tag you once it's PR'd

@derekwaynecarr
Copy link
Member

@pmorie cc me as well. I agree we need this information.

@pmorie
Copy link
Member

pmorie commented Apr 27, 2015

@mfojtik Looks like #6739 will be merged; I think this can be closed.

@mfojtik mfojtik closed this as completed Apr 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/downward-api priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mfojtik @pmorie @derekwaynecarr @bgrant0607 @bprashanth