because my OpenStack K8s cluster with CephFS file shares requires this key, value to be set, but it just does not end up in the container when a new user starts a notebook, it always remains like this:
Newest release 2.0.0. I saw that this setting has been subject to change for the hub itself, where you can set hub.podSecurityContext and hub.containerSecurityContext but when I need containers for users to have these values I’m right in using singelUser as there are no specific values for this in that section of the chart values?
isn’t working. Does it work with other properties? If you’ve got a test deployment could you try the latest dev Helm chart, and if it’s still not working please open a bug report with your configuration and the dev version you tested.
In addition to that there’s a couple of other way you could set that property. Previously every configuration property had to have it’s own corresponding property in the Helm chart. As the number of properties increased it became difficult to keep everything up to date, so for other properties you can set them either using hub.config or hub.extraConfig.
The full list of KubeSpawner config properties is in KubeSpawner — Kubespawner
For example, you could try
but I’m not sure my syntax is correct. Would greatly appreciate it if you could correct me in case it is wrong.
Also, I was wondering if hub: is the correct place for this setting, as I need the securityContext for singelUsers: changed, so user pods/containers have that value set.
Just checking, you’re using hub.config/hub.extraConfig, and not putting those at the top level?
hub:
config:
KubeSpawner:
...
is the correct place. Singleuser containers are managed by the hub, and since the hub creates the Pod specification for those containers it has to manage their configuration.
The singleuser: section of the Helm Chart makes it easier to configure some things, but ultimately most of it is translated into KubeSpawner configuration options.