Now let’s have the Kubernetes Agent do some of the heavy lifting for us to set up our dask pods using the DaskKubernetesEnvironment.
We can use the same agent we made, no problem. But if you haven’t made an agent yet, check the prior section.
Build and register a flow that has the DaskKubernetesEnvironment associated with it. You can change some properties of it such as it’s scaling properties with min_workers or max_workers.
Go ahead and run this flow from the UI and your agent will pick it up. Now if you watch your kubernetes workloads tab closely, you will see that different kubernetes jobs spin up than in the prior section; these are running dask.
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
