#6777 [BUG] Internal & external s3 storage hostname Issue created by sergun ### Flyte & Flytekit version CHART VERSION APP VERSION DESCRIPTION flyteorg/flyte-binary v1.16.2 1.16.0 flytekit==1.16.10 ### Describe the bug I run

pyflyte run --remote

outside k8s cluster and configured storage (minio) with external hostname in `~/.flyte/config.yaml`:

admin:
  endpoint: "flyte.mydomain:443"
storage:
  type: stow
  stow:
    kind: s3
    config:
      auth_type: accesskey
      endpoint: <https://minio.mydomain.com>
      region: ...
      access_key_id: ...
      secret_key: ...

But in the k8s cluster minio is accessible by internal hostname, so I used internal name in flyte-binary helm chart:

configuration:
  storage:
    type: "minio"
    metadataContainer: "flyte"
    userDataContainer: "flyte"
    provider: "s3"
    providerConfig:
      s3:
        region: ...
        authType: "accesskey"
        endpoint: "<http://minio:9000>"
        accessKey: ...
        secretKey: ...
        disableSSL: "true"
        secure: "false"

During:

pyflyte run --remote --project myproject --domain development workflow.py workflow

I got:

resolve 'minio' ([Errno -2] Name or service not known)")

It is weired since I think that

pyflyte run --remote

should execute workflow in k8s cluster where internal hostname

minio

is visible. Anyway I need to use

pyflyte

ouside k8s internal network but want to use internal minio name during workflow execution. How to do this in flyte? ### Expected behavior It should be possible to use pyflyte outside of k8s internal network and use both hostnames of minio storage - internal and external. Internal hostname should be specified in flyte-binary chalm chart and external one - in ~/.flyte/cofig.yaml. ### Additional context to reproduce No response ### Screenshots No response ### Are you sure this issue hasn't been raised already? - [x] Yes ### Have you read the Code of Conduct? - [x] Yes ``` flyteorg/flyte