Why you need this feature:
It would be helpful to know which specific user spawned a notebook in a shared namespace in order to narrow down the owner of a given notebook and also in order to interact with that user data programmatically from within a container (given that $USER is jovyan).
Describe the solution you'd like:
An annotation attached to the notebook pod and / or (preferably and) an env var injected into the notebook with the name of the user who spawned the notebook.
Anything else you would like to add:
It might make sense to incorporate this into pipelines as well.
@droctothorpe: The label(s) kind/feature cannot be applied, because the repository doesn't have them.
In response to [this](https://github.com/kubeflow/notebooks/issues/95):
>/kind feature
>
>**Why you need this feature:**
>It would be helpful to know which specific user spawned a notebook in a shared namespace in order to narrow down the owner of a given notebook and also in order to interact with that user data programmatically from within a container (given that $USER is jovyan).
>
>**Describe the solution you'd like:**
>An annotation attached to the notebook pod and / or (preferably and) an env var injected into the notebook with the name of the user who spawned the notebook.
>
>**Anything else you would like to add:**
>It might make sense to incorporate this into pipelines as well.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
/kind feature
Why you need this feature: It would be helpful to know which specific user spawned a notebook in a shared namespace in order to narrow down the owner of a given notebook and also in order to interact with that user data programmatically from within a container (given that $USER is jovyan).
Describe the solution you'd like: An annotation attached to the notebook pod and / or (preferably and) an env var injected into the notebook with the name of the user who spawned the notebook.
Anything else you would like to add: It might make sense to incorporate this into pipelines as well.