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

Hi,
i’m using helm to create self hosted prefect-worker for my prefect cloud, when i created the worker pool, it is working perfect.
```helm install prefect-worker prefect/prefect-worker -f values.yaml --set-file worker.config.baseJobTemplate=base-job-template.json```
once i have update my  base-job-template.json with some new variables, the helm upgrade is completed successfully, and i can see my change on the configMap, but in the cloud UI, the worker pool is not updating at all.
only after deleting the worker pool, the new one is being created with the relevant changes, but all my flows/deployments are not running, as they are not recognizing my worker pool (is the same name as the deleted one).
We have followed the Kubernetes guide, so why the cloud UI is not updating automatically when running helm upgrade?

<https://github.com/PrefectHQ/prefect-helm/tree/main/charts/prefect-worker#configuring-a-base-job-template-on-the-worker>
The base job template is ignored if the work pool already exists

this sounds like a bug <@U05UAAWNXB4>, what is the workaround to this problem?

I agree that it’s not ideal. We have prefect cli running in our CI/CD pipeline which will update the base job template of the work pool