@Marvin with the transition from agents to workers, is there any equivalent for customizations in a kubernetes worker, allowing arbitrary jsonpatches at deployment time

Yes, with the transition from agents to workers in Prefect, you can still perform customizations in a Kubernetes worker environment, including applying arbitrary JSON patches at deployment time. According to the Prefect documentation, in the Advanced Settings when you're modifying the default base job template for a Kubernetes worker, you can edit the JSON representation of the template to add other fields or delete existing fields. For example, you can set CPU requests by specifying the appropriate JSON structure under

job_configuration

and

containers

. Here are relevant sections in the Prefect Docs you might want to look at for more details: - Kubernetes Deployment Guide - Work Pools Concept They should contain information on how to customize your Kubernetes work pool settings and possibly apply JSON patches to achieve the configuration you need.

not exactly, but you can do something pretty close to it

yeah ok, i was playing with it, so i could add more template variables to make it more customizable. I'm excited about not having to do json patches for resource allocations, which is primarily what i was customizing before.

the resource request and limit fields aren't in the default template, but you can definitely add them yourself. it's also on our to-do list to expose them by default

Is the templating with variables sophisticated, or just straightforward substitution? e.g. is it possible to do conditionals ?

very straightforward

yeah i saw that crop up, very exciting!

np!