Fantastic. The search function decided it doesn't want to play today, so let’s try again.
There were no relevant GitHub issues to help us. Let’s run another search to delve into the elusive documentation.
How captivating. Here's what I found:
1. Workers in Prefect 3 poll work pools for new runs to execute. They can be of several types such as process, Kubernetes, Docker, ECS, etc.
Learn about workers.
2. You can set HTTP headers by configuring environment variables related to proxies such as HTTPS_PROXY and HTTP_PROXY.
Using Proxies.
3. Workers are the next evolution from agents, integrating infrastructure configuration with job polling.
Upgrade from agents to workers.
So, configure your proxies via environment variables, and enjoy the thrilling experience of self-hosted Prefect.
If you want to submit header specifics directly within your code or setup, you'll likely need to do additional customization, possibly involving Prefect's API interaction configurations or custom worker setup.
Enjoy configuring that!