Hi Prefect Team! I am wondering if there is a way to set static

run_config

parameters on a Kubernetes Agent for subsequent flows to consume rather than duplicating similar

run_configs

across various flows. We currently make use of the

PREFECT__CLOUD__AGENT__ENV_VARS

to pass along

storage

configurations, but not having much success attempting to update the execution environment to use an internal custom image. I have tried passing the

IMAGE

and the

PREFECT__CONTEXT__IMAGE

environment variables to my job spec thus far to no avail.

Hi @Zach Hodowanec - thanks for your message. I want to make sure I'm understanding your request and use case correctly. Am I right that what you'd like to do is re-use your run-configs for different flows? You might find this discussion on flow deployment useful but come back if you've got more questions.

Hi @Jenny - thanks for your response. Yes, instead of defining a

flow.run_config = KubernetesRun(image=os.getenv("MY_CUSTOM_IMAGE")

on every flow I was hoping to set something on the agent config itself to override the default execution environment image. Since we know each flow is going to execute on a Kubernetes agent it seems redundant to also define the

flow.run_config

as such. Potentially this issue is more in line with what I'm trying to accomplish?

Thanks Zach. I've checked with the team and I don't think that's possible right now. But I'm going to open an issue to request it. If you want to add any more information in that issue to help us understand your use case, please do! @Marvin open "Enable default run_config on an agent"

One more suggestion is that you could you use job template: https://docs.prefect.io/orchestration/agents/kubernetes.html#custom-job-template

Note that that won't work currently for

image

(fixing that now).

Ok, thank you both! @Jim Crist-Harif Is

flow.run_config = KubernetesRun(image=os.getenv("MY_CUSTOM_IMAGE")

set on each flow the best/recommended way to go about it for now?

Setting on the run config is the best option for now, yeah. Whether using an environment variable is the best way of doing that is up to you.

Great, thanks! Any idea on timeline for making

image

more configurable?

Should be in next release, almost done with the PR

Thanks @Jim Crist-Harif! Just to clarify - this will still require use to use a custom job spec and does not expose the ability to override the

image

for Prefect's default job spec, correct?

This requires the agent to be deployed with a custom job spec, but requires no configuration on the flows.

Great, thanks!