Closed jhamman closed 4 years ago
I'm admittedly not up on many of the details, but think we should go all in on dask gateway!
I'm finishing up some work making dask-gateway more compatible with the other dask clusters, which should make this change easier on your users. I think you may want to keep the user serviceaccounts around for a bit until things have seen more use, but I'd be happy to get things setup in a way that users could try things out.
My short term plan:
closed via #104
I think we're getting to the place where we can start thinking about how to include dask-gateway in this project. Just to quickly summarize some of the motivation for this proposal:
["get", "list", "watch", "create", "delete"]
any pods/services on the cluster. We've long known this is not a long term solution to allowing user to control their dask resourcesDask-gateway gives us the ability to solve both of these problems (and a few more). So what is our path toward adoption of the dask-gateway chart? Is it too soon? Is it missing features we think we should wait for? Would this change require us to disable the RBAC solution or is there a use case for keeping both solutions here?
cc @jcrist, @jacobtomlinson, @TomAugspurger, @yuvipanda