[ 
https://issues.apache.org/jira/browse/SUBMARINE-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chi-Sheng Liu updated SUBMARINE-1184:
-------------------------------------
    Description: 
Get the current namespace with the downward API.

In the beginning I tried to get the current namespace by reading the file 
{{/var/run/secrets/kubernetes.io/serviceaccount/namespace}}. However, not all 
Kubernetes environments have this file. Therefore I decided to use the downward 
API to get the current namespace.

References:
* 
https://stackoverflow.com/questions/31557932/how-to-get-the-namespace-from-inside-a-pod-in-openshift
* 
https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/downward-api.md

  was:Get the current namespace by reading 
{{/var/run/secrets/kubernetes.io/serviceaccount/namespace}} instead of using 
the {{ENV_NAMESPACE}} environment variable.


> Get namespace via Downward API
> ------------------------------
>
>                 Key: SUBMARINE-1184
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-1184
>             Project: Apache Submarine
>          Issue Type: Improvement
>            Reporter: Chi-Sheng Liu
>            Assignee: Chi-Sheng Liu
>            Priority: Major
>              Labels: pull-request-available
>
> Get the current namespace with the downward API.
> In the beginning I tried to get the current namespace by reading the file 
> {{/var/run/secrets/kubernetes.io/serviceaccount/namespace}}. However, not all 
> Kubernetes environments have this file. Therefore I decided to use the 
> downward API to get the current namespace.
> References:
> * 
> https://stackoverflow.com/questions/31557932/how-to-get-the-namespace-from-inside-a-pod-in-openshift
> * 
> https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/downward-api.md



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to