Replies: 1 comment 1 reply
-
The storage configuration for Flyte backend is driven using the Config you pointed to. But, if you notice this is a template. We have simplified the installation on AWS and GCP, but you can ofcourse use the RAW configuration options to use non cloud storage backends. This can be seen in the template here Thus, lets say you want to configure MINIO on-prem, then the configuration should look something like this
Note you still need to provide the region, as the minio is simply an emulation of S3 client. If you want to provide even more raw configuration then refer to stow. this is the library Flyte uses to connect with the various backends The configuration should look like
An example for configuring
|
Beta Was this translation helpful? Give feedback.
-
I'm try to deploy a test version of Flyte with the Helm chart, I'm not hosting on Google or Amazon, but I have got an S3 storage, so how can I try to customize the storage section with an individual endpoint for using S3: https://github.com/flyteorg/flyte/blob/master/charts/flyte/values.yaml#L473-L485
e.g. I need flags to setup the endpoint, s3 key and secret and enable HTTPS
Beta Was this translation helpful? Give feedback.
All reactions