We have a fresh install of jupyterhub using the guidelines on Zero to JupyterHub with Kubernetes — Zero to JupyterHub with Kubernetes documentation. We have configured quite aggressive. And I think this might be the conditions at this time.
The kernel says connecting, and then goes to disconnected, so no cell executions is possible. Following troubleshooting on What to do when things go wrong — Jupyter Notebook 6.5.2 documentation gave the following output:
$ jupyter kernelspec list Available kernels: python3 /opt/conda/share/jupyter/kernels/python3
And the Terminal is just staying idle in the start. As in the screenshot.
My assumption is the changes to the rights here so we simply don’t have the rights to execute anything that the ops set up. If this is not the case, please point me in a direction to continue debugging. Here is the config changes I think might be the issue where we deny the terminal and python kernel to actually execute. Not sure what to allow here either.
... podSecurityContext: fsGroup: 1000 seccompProfile: type: RuntimeDefault runAsNonRoot: true ... containerSecurityContext: runAsUser: 1000 runAsGroup: 1000 allowPrivilegeEscalation: false privileged: false capabilities: drop: - ALL ... chp: revisionHistoryLimit: containerSecurityContext: runAsUser: 65534 # nobody user runAsGroup: 65534 # nobody group allowPrivilegeEscalation: false privileged: false capabilities: drop: - ALL