Sure, workers are intended to be much more tightly coupled to the infrastructure.
Some of these issues we saw with agents, was there was too much customization, and some users got themselves stuck trying to do something in one way that was un-intuitive.
Workers couple infrastructure to the work-pool - that is, a Docker work pool handles, docker based flow runs, and all related configuration
Kubernetes workers manage k8s work-pools, and you customize that base job template right on the worker.
As a result, all flows / deployments that use that work-pool, will receive that configuration as a default, which you can overide / customize as needed.
The advantage is it can separate configuration / infrastructure for someone who might just be a code author and know nothing about hte underlying infrastructure