New RunLLM response generated: >>>*# Question* Hi everyone, we are bound to an on-prem solution for k8s and are evaluating flyte atm. Is there a good starter for self-hosted flyte that does not use any of the big three (GCP, AWS, AZURE)? Value files all seem to be referencing them. # Answer For an on-premises Kubernetes deployment of Flyte without using GCP, AWS, or Azure, you can use the Helm chart with custom values. According to this discussion, you can deploy Flyte on a local Kubernetes cluster by configuring the necessary dependencies like PostgreSQL for metadata and MinIO for object storage. Here's a basic outline to get you started: 1. Add Flyte Helm Repository:

helm repo add flyteorg https://helm.flyte.org
    helm repo update

2. Install Flyte with Custom Values: Create a custom

values.yaml

file to override the default settings. Below is an example configuration:

configmap:
      adminServer:
        server:
          httpPort: 8088
          grpcPort: 8089
          dataProxy:
            upload:
              storagePrefix: upload
          security:
            secure: false

    postgres:
      enabled: true
      postgresqlPassword: yourpassword

    minio:
      enabled: true
      accessKey: minio
      secretKey: minio123

3. Deploy Flyte:

helm install flyte flyteorg/flyte-core -n flyte -f values.yaml

Would you like more detailed steps or specific configurations for your setup? Sources: - Flyte on k3s - POC an on-premise full installation Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1724681798.138869 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.