-
Notifications
You must be signed in to change notification settings - Fork 5
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
ConnectionRefusedError when running Marimo in kubernetes deployed Jupyterhub #5
Comments
@ZazenX Can you locally patch this line?
Maybe
To see if that works? Otherwise you can put a proxy on top and forward traffic |
Thank you for investigating this issue. I don't have the capability to work on it myself (not familiar with Kubernetes) but would be happy to incorporate a fix. |
That seemed to do the trick! Cloned the repo and |
@ZazenX Could you also test |
@akshayka @marimo-team, tagging you in this as dicussed on Discord.
I am having issues deploying Marimo to a k3s cluster. I am able to open the notebook from the launcher, and even pick an existing *.py notebook from the workspace explorer.
Deploying and testing locally on minikube works just fine, I can open marimo from the jupyterlab launcher and write and execute notebooks. When deployed on our k3s cluster on our servers though we run into errors like the ones attached. When the marimo interface opens, I get ConnectionRefusedErrors from the singleuser pod.
Opening files from the jupyter-server-proxy seems to refuse connections from the marimo api.
The text was updated successfully, but these errors were encountered: