-
Notifications
You must be signed in to change notification settings - Fork 223
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
JEG 3.2.3 on K3s v1.28.5 unable to start kernels. Same actions with helm chart 3.2.2 pyspark kubernetes work. #1379
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Okay so the culprit is the updated kubernetes pip version. EG 3.2.2 has 26.1.0 kubernetes python ver, EG 3.2.3 has 29.0.0
I hope will find time to try to fix this
So this code cant execute: |
Could this probably be related to new Kubernetes Client version where these have changed? |
@lresende see my reply above |
So, we should cap the kubernetes client for now I would say |
@paf91 |
Description
Whenever I start kernel based on kubernetes I'm getting this error on version 3.2.3:
Error Starting Kernel
HTTP 500: Internal Server Error (Error from Gateway: [Error occurred creating role binding for namespace 'guest-fab3e59b-edbb-4e1d-912e-087b1798425b': module 'kubernetes.client' has no attribute 'V1Subject'] Error occurred creating role binding for namespace 'guest-fab3e59b-edbb-4e1d-912e-087b1798425b': module 'kubernetes.client' has no attribute 'V1Subject'. Ensure gateway url is valid and the Gateway instance is running.)
Reproduce
values.yaml:
helm upgrade --install enterprise-gateway https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.2.3/jupyter_enterprise_gateway_helm-3.2.3.tar.gz --namespace enterprise-gateway -f ~/jupyter/gateway/values-balancer.yaml
kubectl get pods -n enterprise-gateway:
Try to run:
`curl -X POST -i 'http://<redacted_private_ip>:8888/api/kernels' --data '{ "name": "spark_python_kubernetes", "env": { "KERNEL_USERNAME": "jovyan" }}'`
Response:
Enterprise gateway logs:
kubectl logs -n enterprise-gateway enterprise-gateway-cfbb54797-7dph8
Expected behavior
Kernel starts
Context
JEG 3.2.3 on K3s v1.28.5
The text was updated successfully, but these errors were encountered: