Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Another small question: the <https://docs.prefect.io/orchestration/execution/dask_k8s_environment.html#examples|docs for the Dask Kubernetes Environment> show an example where they set `--memory-limit 4GB`  in the `dask-worker` command but also set a memory limit of `memory: 4G` in the Kubernetes `resources` . Are both required for correct functionality?

I don’t believe both are required! Setting the limit on the dask worker should be enough to have the intended effect