Hi all, Newbie here! we are considering using Flyte for LLM fine-tuning workflows. I am trying to deploy single cluster simple cloud deployment following this : https://docs.flyte.org/en/latest/deployment/deployment/cloud_simple.html - Created a Postgres (CloudSQL) instance, database, user - Created a GCS bucket "flyte-poc-data" - Created Service Account "dev01-flyte-poc-sa" with GKE,GCS Admin access. Since the documentation doesn't include a config for GKE , I created values.yml as follows:

configuration:
  database:
    username: flyte_user
    password: {password}
    host: 192.{db ip}
    port: 5432
    dbname: flyte
  storage:
    metadataContainer: flyte-poc-data
    userDataContainer: flyte-poc-data
    provider: gcs
    providerConfig:
      gcs:
        project: "{our GCP project id}"
serviceAccount:
  create: false
  name: dev01-flyte-poc-sa

helm install executed without any errors. But I only see Services and Deployments in k8s. There are NO pods created. Any idea ?

helm install flyte-backend flyteorg/flyte-binary --namespace flyte --values gcp-values.yml

W0911 15:41:23.101181   33738 warnings.go:70] autopilot-default-resources-mutator:Autopilot updated Deployment flyte/flyte-backend-flyte-binary: defaulted unspecified resources for containers [wait-for-db, flyte] (see <http://g.co/gke/autopilot-defaults>)
NAME: flyte-backend
LAST DEPLOYED: Mon Sep 11 15:41:20 2023
NAMESPACE: flyte
STATUS: deployed
REVISION: 1
TEST SUITE: None

Can you pls do

kubectl -n flyte describe deployment <name>

and paste the output?

Hi @Fabio Grätz thank you. Pod started after i changed "create:false" to "create:true" :

serviceAccount:
  create: true

Now the pod fails because the it doesn't have GCS access.(I can see the postgres tables are initialized) Will figure out how to apply the right access to the SA.

Cool

Thank you, i managed to resolve the iam permissions using https://cloud.google.com/model-garden , Cluster is up and running fine 👍