-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Update dask-kubernetes to a newer kr8s #853
Comments
@jacobtomlinson , could you please specify what exactly has been broken? Is it related to #848, or are there any other tickets? |
@dbalabka I think |
@jacobtomlinson , I noticed the changes in the port forwarding. As far I understood, dask-kubernetes uses a new way to forward ports. I tested it and it fixes the problem with websockets for us. Therefore, we don't need to use NodePort any more. |
@jacobtomlinson I will perform more tests and give a feedback in #805 |
Recently we unpinned
kr8s
but things broke, so the pin was set back to0.9.0
. We need to manually update the pin to something more recent (and in theory more stable) before unpinning again.The text was updated successfully, but these errors were encountered: