Super simple question: I am running a

@task

using

remote.execute

with the arg

options=Options(labels=Labels({"test_label": "test_value"}))

and I cannot seem to get that label to attach to the pod in kubernetes, however this same setup works when I call this using a

@workflow

and I can see my

"test_label"

label added to all pods spun up by the workflow, is this to be expected? If so is there a way to attach pod labels when running

remote.execute

just on a

@task

?

@David Espejo (he/him) do you know the answer to this?

To be clear here I am executing with

FlyteRemote(...).execute(example_task, options=options, ...)

let me try to take a look tonight…

Thanks from the docs it looks like Options should apply to workflows as well as tasks, so I wanted to ask to confirm.

sorry, I'm not sure yet but will keep investigating later

Sweet thanks all, really appreciate it.

is this a local task? (ie a task defined in your .py file) as opposed to a “remote task” (ie the output of remote.fetch_task(…))

I am executing it as a remote task, from python code. So I guess it would qualify as a locally defined task. I can open a PR for this yeah. The task is simply defined as this that we are running

remote.execute

on

import logging
from flytekit import dynamic, task, workflow

@task
def my_task(input: str) -> str:
    return input

okay…

The latter

so yeah that’s a locally defined task, so the options arg appears to be missing

Okay, I can open a PR for this this week