Christopher Ostrouchov
Christopher Ostrouchov
This needs to be tested and see if it disappears but I believe this should be resolved.
Completely agree. Was planning to leave this untill our next release. But you are right that this is needed.
@dharhas we probably need to talk about https://github.com/Quansight/qhub/blob/main/qhub/template/stages/07-kubernetes-services/modules/kubernetes/services/conda-store/config/conda_store_config.py#L74-L99. This mainly has to do with how I have the user's setup with group role mappings would be my guess. I've worked...
@dhirschfeld thanks for joining in the conversation. Yes I agree and do see some issues using this project long term. We will be talking this issue in around 3 months...
@iameskild this has to do with a change that I made in the container default uid/gid. I'll provide a fix tomorrow morning
I agree having a feature like this would be useful and help to separate development based additions to qhub.
@viniciusdc yes we just drop permissions for users with this given namespace and they will no longer see it.
See: - https://github.com/jupyterhub/kubespawner/issues/546 - https://github.com/jupyterhub/jupyterhub/issues/3592 So should potentially rename this issue upgrade QHub to use latest jupyterhub 2.2.0+ version.
Let me talk in detail a bit more about these pieces. # OAuth2 Provisioning We should provision an OAuth2 client per service with keycloak this is possible an encouraged. Should...
I like it @Adam-D-Lewis and nice in that it is definitely the minimum that would be useful and would not introduce complex dependencies on QHub bits.