Hey there again everyone Hopefully a quick question about do

Question

Hey there again everyone Hopefully a quick question about doing a `create flow run run flow name= flow 2 ` within a task created by a `KubernetesRun` assuming i have ```with Flow flow 1 run config=KubernetesRun creates task that does a create flow run run flow name= flow 2 ``` should `flow 2` receive inherit the `run config` from `flow 1`

Kevin Kho · Answer

There is no RunConfig inheritance It has to be defined on the subflow but I think you can explicitly pass a new RunConfig as well if you want It s more common though to pass parameters down to link the parent and child

Kevin Kho · Answer

`create flow run` can take in a RunConfig <https docs prefect io api latest tasks prefect html create flow run|here>

Christian Nuss · Answer

thanks < Kevin Kho> then thats what i experienced and wanted to make sure i wasn t crazy or doing something wrong also your response time for questions here is on point star star star star star

Kevin Kho · Answer

Thank you

William Grim · Answer

< Kevin Kho> in this case flow 2 would also have been defined registered and serialized with a KubernetesConfig i think < Christian Nuss> was seeing that it wasn t working though i e the labels defined in the flow being called from the first KubernetesRun weren t set

William Grim · Answer

i worded that awkwardly let me rephrase

William Grim · Answer

I believe he was seeing that the registered flow which was being called by the first flow which was instantiated as a KubernetesRun wasn t getting its run config labels set on it when it was instantiated even though it s defined in the flow itself Is that right < Christian Nuss>

William Grim · Answer

still awkward but hopefully less so

Christian Nuss · Answer

right correct as < William Grim> said we have a `with Flow flow 2 run config=KubernetesRun ` registered

Kevin Kho · Answer

Ah ok so you have a subflow registered with KubernetesRun but it doesn t seem respected What do you see when you go to the Flow page in the UI There should be a space for RunConfig and labels

Christian Nuss · Answer

1 sec standby

Christian Nuss · Answer

strange its adding a nonsense label

Christian Nuss · Answer

so its not getting scheduled

Kevin Kho · Answer

Ah ok before you register you can do ```flow storage add default labels = False``` and then try re registering

Kevin Kho · Answer

Wait so you have pending runs but the create flow run is working right

Christian Nuss · Answer

create flow run does appear to be working as the new sub flow gets registered and the run config looks correct so just a labeling issue

Kevin Kho · Answer

Gotcha yeah just remove the default label and I think this should be good What storage are you using though Normally the default label is attached to local storage

Christian Nuss · Answer

i made some hackery in this case with volume mounts for Local Development purposes

Kevin Kho · Answer

Ohhh yes ok that sounds good and you can turn off the default label that is part of Local storage

Christian Nuss · Answer

rocket

Christian Nuss · Answer

worked like a charm thx

Christian Nuss · Answer

in Production we will use S3 Storage + Kube do you think i should add the `add default labels=False` there too feels like i should for consistency

William Grim · Answer

< Christian Nuss> i believe the nonsense label is your instance s hostname

Anna Geller · Answer

no need for add default labels when using S3 storage it s only applied when using local storage and William is correct this cac0475 is the hostname of your machine slightly smiling face