You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have to inject some secret information into each SingleUser container (i.e ssh private keys, credential files etc), by using "extraFiles" setup this keeps all this information in plaintext and available. There should be a way to be able to store this information in a secret/configmap outside of the helm instalation
Alternative options
Potentially we can do this with an initContainer, however this seems slightly excessive.
Who would use this feature?
Anybody that needs to setup a user environment to have access to external servers
(Optional): Suggest a solution
Add a volume mount setup for the extra files that you can reference a secret or configmap. i.e
You can use singleuser.extraVilumes and singleuser.extraVolumeMounts for this though right? I figure mixing this into extraFiles is messier than needed with those options available as well
Proposed change
Currently we have to inject some secret information into each SingleUser container (i.e ssh private keys, credential files etc), by using "extraFiles" setup this keeps all this information in plaintext and available. There should be a way to be able to store this information in a secret/configmap outside of the helm instalation
Alternative options
Potentially we can do this with an initContainer, however this seems slightly excessive.
Who would use this feature?
Anybody that needs to setup a user environment to have access to external servers
(Optional): Suggest a solution
Add a volume mount setup for the extra files that you can reference a secret or configmap. i.e
The text was updated successfully, but these errors were encountered: