I started looking at Dask recently... its scheduler/worker mechanism reminded me of the old Docker Swarm. I liked that! But when I moved to a Kubernetes deploy

I started looking at Dask recently... its scheduler/worker mechanism reminded me of the old Docker Swarm. I liked that! But when I moved to a Kubernetes deployment (set up via the community provided Helm charts), I was completely mystified and got slowdowns as reported by others. At one point my physical worker node was using 1 core, and at other times, it was using all cores. When I dug into the default config they provide, it should have been 2 vcpus. So .. all in all .. I was completely mystified what was going on under the hood, which speaks to the lack of debugging mentioned by people.