https://flyte.org logo
#ask-the-community
Title
# ask-the-community
b

Broder Peters

01/25/2024, 1:51 PM
Hello, I have to configure my local flyte config to access minio under a specific port. I assumed that would happen in my
.flyte/config.yaml
.
Copy code
admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///<my-flyte-domain>
  authType: Pkce
storage:
  connection:
    endpoint: http://<mycustomminiodomain>:<custom-port>
Wouldn't I do that over the
endpoint
setting? After adjusting the config
pyflyte run --remote
still runs again
host='minio.flyte.svc.cluster.local', port=9000
d

David Espejo (he/him)

01/25/2024, 6:54 PM
Hey Broder So this it set at the platform level but you need to override it? Or it would be better to set the custom port at the platform level?
b

Broder Peters

01/26/2024, 9:11 AM
Do you mean by platform level the environment where flyte is deployed in?
d

David Espejo (he/him)

01/26/2024, 3:35 PM
I mean, at the Helm chart config level
b

Broder Peters

01/26/2024, 3:41 PM
at helm level I've setup minio with default parameters I think. Services looks like this:
flyte                  minio                                NodePort       <someip>    <none>        9000:30084/TCP,9001:30088/TCP
My issue is that I won't get port 9000 opened on the on premise server soon and therefore thought I could just utilize the open port
30084
as well for my
pyflyte
execution
d

David Espejo (he/him)

01/29/2024, 5:19 PM
so, in that case you should be port-forwarding to a local custom port like
kubectl -n flyte port-forward service/minio <custom>:9000
Then, the
storage
section should let you override the Helm config for pyflyte
b

Broder Peters

01/30/2024, 7:59 AM
Yeah sorry I forgot to mention that ideally it should be possible without kubectl /: But I'm going to try another idea today. Long story short. this topic should be solved anyway properly by opening the servers ports on the long run...