How do you specify remote settings when running eager workflows? IM setting env for the FLYTE_PLATFORM_URL but there is no env for insecure setting I am running in k8s, and the grcp endpoint is flyteadmin.flyte.svc.cluster.local:81. However, cannot set this to be insecure=true:

remote = FlyteRemote(
    config=Config.for_endpoint(
        endpoint="flyteadmin.flyte.svc.cluster.local:81",
        insecure=True
    ),
    default_project="flytesnacks",
    default_domain="development"
)
@eager(remote=remote)
async def my_teast(input_file: str, output_file: str, open_api_key: str):
    pass

However, when the task runs in the pod:

│ {"asctime": "2025-03-21 12:18:46,341", "name": "flytekit", "levelname": "WARNING", "message": "Auto-created config object to pick up env vars Config(platform=PlatformConfig(endpoint='flyteadmin.flyte.svc.cluster.local:81', insecure=False,

Based on the docs

**Environment Variables**: Users can specify these at compile time, but when your task is run, Flyte Propeller will
also set configuration to ensure correct interaction with the platform. The environment variables must be specified
with the format ``FLYTE_{SECTION}_{OPTION}``, all in upper case. For example, to specify the
:py:class:`PlatformConfig.endpoint <flytekit.configuration.PlatformConfig>` setting, the environment variable would
be ``FLYTE_PLATFORM_URL``.

https://github.com/flyteorg/flytekit/blob/5503ee5e232fdbc633af39c7f4539a04906102fc/flytekit/configuration/__init__.py#L20-L24 So maybe try

FLYTE_PLATFORM_INSECURE

?

cabt we specify in our config.yaml like here

authType: Pkce
  insecure: false
  insecureSkipVerify: false
logger:
  show-source: true
  level: 6

I'm not sure but I'll note that the

config.yaml

applies to the flyte control/data plane and not necessarily the pod your container runs in.

@clean-glass-36808 i will try FLYTE_PLATFORM_INSECURE What i ended up doing was a PodTemplate that mounts a config map and then i set FLYTECTL_CONFIG to that file

but internally on EKS doent its call like on svc.cluster.local no??

that is just the DNS of the k8s admin . EagerWorkflows use FlyteRemote and when running in sandbox i am assuming its just pointing to localhost, but when deployed without setting the platform URL eager workflows will fail

@damp-hamburger-67475

i will try FLYTE_PLATFORM_INSECURE

Did this work for you?