Shaariq
09/22/2023, 5:11 AMhelm
chart. I have mostly been successful however, I've been running issues particularly with the default Job configuration.
Even though I am setting the usual namespace to prefect
, the default Job config seems to always be default
. Ideally I don't want to have to do an infra_override
for each flow that I create, and so is it possible to have each job that is generated to be created with a configurable namespace? Or to use the namespace that has been set for the worker/server?
To go further on the steps I take:
• install helm chart as specified above^
• deploy my flow with the correct workpool name
• run my flow
The expectation here is that the flow-run should trigger a kubernetes job creation in the same namespace prefect
. However, it creates the job in default
because that is what the workpool appears to be set to.
If I am missing anything, please do let me know as well. I am having a lot of fun with Prefect otherwise, Cheers!
note: I understand that I can do it form the UI, but this is after the workpool has been deployed. not ideal. Rather declare it earlier onBring 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.
Powered by