-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhancement] configure prefect agent labels and environment variables #764
Comments
Thanks for opening this. There isn't a way do this currently, however, we would welcome a PR. If you did decide to work on this then I'd suggest that we modify the helm chart currently being used to deploy Prefect to be closer to the one used in the official Prefect Server helm chart (https://github.com/PrefectHQ/server/blob/master/helm/prefect-server/templates/agent/deployment.yaml). I see that they do have a way to include arbitrary prefect labels, but not arbitrary environment variables. We could add the arbitrary environment variables with the range action in helm. The rest of the changes are fairly minor modifications to qhub. Would you be interested in contributing a PR, @jhamman? |
@Adam-D-Lewis - see #768 for an initial attempt. |
Some thoughts here |
Just adding a bit more context here - the Prefect Helm chart does not have specific fields for is this idea of having |
We have a working version now merged in from #813 which allows you to define arbitrary environment variables on the prefect agent and add labels to the prefect agent. Closing this issue since this is now resolved. |
Description
I would like to set labels and environment variables on my prefect agents. Is this possible today? Or does this require a new feature in qhub?
Suggestion
Perhaps the prefect configuration section could look something like this:
Context
Our prefect cloud account has multiple agents attached to it. Exposing labels and env_vars via the qhub config would allow us to preferentially direct flows to the correct agent.
The text was updated successfully, but these errors were encountered: