so absolutely dying trying to get this deployed in EKS -- namely on minio charts are effectively the same so I am not sure why minio all the sudden just doesnt work

flytekit.exceptions.user.FlyteAssertion: Failed to put data from /tmp/tmp030l19_7/script_mode.tar.gz to <http://localhost:30084/my-s3-bucket/a/b/PJPRTCSJDCALQRYI44IFNWNQ5M%3D%3D%3D%3D%3D%3D/scriptmode.tar.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minio%2F20230315%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230315T152958Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-md5%3Bhost&X-Amz-Signature=9b449916e2b9ca077d45255d05f86fec463c3e999e14c2c38a0075928906afa0> (recursive=False).

Original exception: HTTPConnectionPool(host='localhost', port=30084): Max retries exceeded with url: /my-s3-bucket/a/b/PJPRTCSJDCALQRYI44IFNWNQ5M%3D%3D%3D%3D%3D%3D/scriptmode.tar.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minio%2F20230315%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230315T152958Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-md5%3Bhost&X-Amz-Signature=9b449916e2b9ca077d45255d05f86fec463c3e999e14c2c38a0075928906afa0 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f205d87edc0>: Failed to establish a new connection: [Errno 111] Connection refused'))

noticed it was using a signed url override (not sure why it's doing that all of the sudden) and pretty much anything I change/update in the charts just doesnt apply, for example:

storage:
      # -- Sets the storage type. Supported values are sandbox, s3, gcs and custom.
      type: sandbox 
      # -- bucketName defines the storage bucket flyte will use. Required for all types except for sandbox.
      bucketName: my-s3-bucket 
      # -- settings for storage type s3
      signedUrl:
        stowConfigOverride:
          endpoint: <http://minio.flyte.svc.cluster.local:9000>

anyone have any thoughts?

@justin hallquist hopefully that was pun intended - please do not die

so setting up s3 as the backend also proved very problematic

error log says it’s trying to connect at localhost:30084

sure and i can't seem to update the

stowConfigOverride

to address that

are you copying config from flyte-sandbox?

@Ketan (kumare3) im not sure why, as a backend meta store for flyte, minio would be an issue if self hosted interm -- pointing at that or at s3 should be the same except config which is kinda the point of minio acting as a drop in interface from my understanding

and you can drop the stow config override unless you want to port-forward and use signed URLs.

would love to drop the stow config stuff, for some reason it's signed off the bat and i dont know why and as mentioned, i cant seem to update it

hmm how are you deploying,

if you look at the override above, i am trying to set it to the k8s fqdn

try this one: https://github.com/flyteorg/flyte/tree/master/charts/flyte-binary

k so would really prefer not to change charts atm as the team uses a local version of the

flyte/flyte

chart that works great and we're setting this up for enterprise and would like the ability to have more configuration options

right ok

ya one sec

that’s mostly only for minio. you can just use IRSA for allowing your tasks to talk to s3

my workflows/tasks communicate fine with s3 when i do

pyflyte run

my understanding is the code is packaged and stored ... somewhere i think im confused as I can't seem to get that storage to work with either minio or s3

yes the flyte control plane also needs access to a bucket to store metadata

right -- and is that not configurable through the chart?

it should be

values.yaml

why are there 2 remoteData?

that's how the chart is set up: https://github.com/flyteorg/flyte/blob/master/charts/flyte/values.yaml#L555

ah ok

kk will try that