Hey
@gray-jordan-61319, I'm not able to reproduce this here. All subworkflows are adopting the parent workflows Pod labels. Using your example
FlyteRemote
commands:
from flytekit.configuration import Config, PlatformConfig
from flytekit.models.common import Labels
from flytekit.remote import FlyteRemote
from flytekit.remote.remote import Options
import os
config = Config.for_endpoint("localhost:8089", insecure=True)
remote = FlyteRemote(config=config)
workflow = remote.fetch_workflow(project="flytesnacks", domain="development", name="core.control_flow.subworkflows.parent_wf", version="v0.3.100")
remote.execute(workflow, inputs={"a": 1}, options=Options(labels=Labels({"flyte.user": os.getenv("USER", "na")})), project="flytesnacks", domain="development")
where the workflow is one of our
flytesnacks subworkflow tests I am seeing all the pods (including those launched by the subworkflow) have the correct labels set:
hamersaw@ragnarok:~$ kubectl -n flytesnacks-development get pod fc09411a31e134117aaa-node-t1-parent-0 -o yaml
apiVersion: v1
kind: Pod
metadata:
labels:
flyte.user: hamersaw
// ...
hamersaw@ragnarok:~$ kubectl -n flytesnacks-development get pod fc09411a31e134117aaa-n1-0-n0-0 -o yaml
apiVersion: v1
kind: Pod
metadata:
labels:
flyte.user: hamersaw
// ...
hamersaw@ragnarok:~$ kubectl -n flytesnacks-development get pod fc09411a31e134117aaa-n1-0-n1-0 -o yaml
apiVersion: v1
kind: Pod
metadata:
labels:
flyte.user: hamersaw
// ...
