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

Added doc example of mounting k8s secrets as ENV variables to user pods without values.yaml #1462

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions doc/source/advanced.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,28 @@ hub:
# some other code
```

Example of mounting kubernetes secrets as environmeent variables into spawned user pods via `hub.extraConfig` without having to expose them in your `values.yaml`. Useful for example, if you want to provide credentials for reading protected external resources.

```yaml
hub:
extraConfig:
...
10-secretToEnv: |
from kubernetes import client
def modify_pod_hook(spawner, pod):
pod.spec.containers[0].env.append(
client.V1EnvVar(
name='YOUR_ENV_VARIABLE',
value_from=client.V1EnvVarSource(
secret_key_ref=client.V1SecretKeySelector(
name='your-secret',
key='SECRET_KEY',
))))
return pod
c.KubeSpawner.modify_pod_hook = modify_pod_hook
...
```

### `custom` configuration

The contents of `values.yaml` is passed through to the Hub image.
Expand Down