Hello All, I am having microk8s cluster created. I have installed flyte using chart below

root@flyte:~# microk8s helm install flyte flyteorg/flyte-core \
  --namespace flyte \
  --create-namespace \
  --set minio.enabled=true \
  --set postgresql.enabled=true
NAME: flyte
LAST DEPLOYED: Wed Mar 26 12:14:00 2025
NAMESPACE: flyte
STATUS: deployed
REVISION: 1
TEST SUITE: None
root@flyte:~# microk8s kubectl get pods -n flyte
NAME                                READY   STATUS                  RESTARTS     AGE
datacatalog-5989c784-s8zzl          0/1     Init:CrashLoopBackOff   1 (4s ago)   5s
flyte-pod-webhook-cddbb7865-vbjgt   0/1     Init:0/1                0            5s
flyteadmin-674c7886b9-r5g7s         0/1     Init:CrashLoopBackOff   1 (3s ago)   5s
flyteconsole-c5bdbbfc5-6jk8g        1/1     Running                 0            5s
flytepropeller-6fc8574d58-jd5wg     1/1     Running                 0            5s
syncresources-74bbb5798f-tx289      0/1     CrashLoopBackOff        1 (3s ago)   5s

I gather this is because of

root@flyte:~# microk8s kubectl events datacatalog-5989c784-s8zzl -nflyte
LAST SEEN              TYPE      REASON    OBJECT                               MESSAGE
3m38s (x70 over 18m)   Warning   BackOff   Pod/syncresources-74bbb5798f-tx289   Back-off restarting failed container sync-cluster-resources in pod syncresources-74bbb5798f-tx289_flyte(602a779d-68ed-4c84-978c-4db7374f3996)
3m35s (x72 over 18m)   Warning   BackOff   Pod/datacatalog-5989c784-s8zzl       Back-off restarting failed container run-migrations in pod datacatalog-5989c784-s8zzl_flyte(b9976245-4895-4d6d-8f07-a0fa3218195e)
3m29s (x70 over 18m)   Warning   BackOff   Pod/flyteadmin-674c7886b9-r5g7s      Back-off restarting failed container run-migrations in pod flyteadmin-674c7886b9-r5g7s_flyte(621c3341-c6cd-4333-96d8-0158cade8e73)
2m48s (x9 over 18m)    Normal    Pulled    Pod/syncresources-74bbb5798f-tx289   Container image "cr.flyte.org/flyteorg/flyteadmin-release:v1.15.0" already present on machine
2m48s (x9 over 18m)    Normal    Created   Pod/syncresources-74bbb5798f-tx289   Created container: sync-cluster-resources
2m48s (x9 over 18m)    Normal    Started   Pod/syncresources-74bbb5798f-tx289   Started container sync-cluster-resources
2m37s (x9 over 18m)    Normal    Pulled    Pod/datacatalog-5989c784-s8zzl       Container image "cr.flyte.org/flyteorg/datacatalog-release:v1.15.0" already present on machine
2m37s (x9 over 18m)    Normal    Created   Pod/datacatalog-5989c784-s8zzl       Created container: run-migrations
2m37s (x9 over 18m)    Normal    Started   Pod/datacatalog-5989c784-s8zzl       Started container run-migrations
2m34s (x9 over 18m)    Normal    Pulled    Pod/flyteadmin-674c7886b9-r5g7s      Container image "cr.flyte.org/flyteorg/flyteadmin-release:v1.15.0" already present on machine
2m34s (x9 over 18m)    Normal    Created   Pod/flyteadmin-674c7886b9-r5g7s      Created container: run-migrations
2m34s (x9 over 18m)    Normal    Started   Pod/flyteadmin-674c7886b9-r5g7s      Started container run-migrations
root@flyte:~# microk8s kubectl events flyteadmin-674c7886b9-r5g7s -nflyte
LAST SEEN              TYPE      REASON    OBJECT                               MESSAGE
4m25s (x70 over 19m)   Warning   BackOff   Pod/syncresources-74bbb5798f-tx289   Back-off restarting failed container sync-cluster-resources in pod syncresources-74bbb5798f-tx289_flyte(602a779d-68ed-4c84-978c-4db7374f3996)
4m22s (x72 over 19m)   Warning   BackOff   Pod/datacatalog-5989c784-s8zzl       Back-off restarting failed container run-migrations in pod datacatalog-5989c784-s8zzl_flyte(b9976245-4895-4d6d-8f07-a0fa3218195e)
4m16s (x70 over 19m)   Warning   BackOff   Pod/flyteadmin-674c7886b9-r5g7s      Back-off restarting failed container run-migrations in pod flyteadmin-674c7886b9-r5g7s_flyte(621c3341-c6cd-4333-96d8-0158cade8e73)
3m35s (x9 over 19m)    Normal    Pulled    Pod/syncresources-74bbb5798f-tx289   Container image "cr.flyte.org/flyteorg/flyteadmin-release:v1.15.0" already present on machine
3m35s (x9 over 19m)    Normal    Created   Pod/syncresources-74bbb5798f-tx289   Created container: sync-cluster-resources
3m35s (x9 over 19m)    Normal    Started   Pod/syncresources-74bbb5798f-tx289   Started container sync-cluster-resources
3m24s (x9 over 19m)    Normal    Pulled    Pod/datacatalog-5989c784-s8zzl       Container image "cr.flyte.org/flyteorg/datacatalog-release:v1.15.0" already present on machine
3m24s (x9 over 19m)    Normal    Created   Pod/datacatalog-5989c784-s8zzl       Created container: run-migrations
3m24s (x9 over 19m)    Normal    Started   Pod/datacatalog-5989c784-s8zzl       Started container run-migrations
3m21s (x9 over 19m)    Normal    Pulled    Pod/flyteadmin-674c7886b9-r5g7s      Container image "cr.flyte.org/flyteorg/flyteadmin-release:v1.15.0" already present on machine
3m21s (x9 over 19m)    Normal    Created   Pod/flyteadmin-674c7886b9-r5g7s      Created container: run-migrations
3m21s (x9 over 19m)    Normal    Started   Pod/flyteadmin-674c7886b9-r5g7s      Started container run-migrations

I did create flyte-values.yaml as like below

postgresql:
  enabled: false
  external:
    host: postgres-postgresql.default.svc.cluster.local
    user: postgres
    password: XXXXXXXXXXX
    database: postgres
    port: 5432

minio:
  enabled: false
  existingSecret: ""
  serviceEndpoint: <http://minio.default.svc.cluster.local:9000>
  accessKey: minioadmin
  secretKey: XXXXXXXXXXXXX

datacatalog:
  initContainersEnabled: true

flyteadmin:
  db:
    password: WonderfulSwiss12#$

  storage:
    provider: s3
    container: my-s3-bucket
    endpoint: <http://minio.default.svc.cluster.local:9000>
    accessKey: minioadmin
    secretKey: minioadmin123
    region: us-east-1
    disableSSL: true

flytepropeller:
  storage:
    provider: s3
    container: my-s3-bucket
    endpoint: <http://minio.default.svc.cluster.local:9000>
    accessKey: XXXXXXXXXXX
    secretKey: XXXXXXXXXXXXXX
    region: us-east-1
    disableSSL: true

and deployed helm chart with values yaml. Is there a proper chart which will install all seamlessly without any issues? I did use sandbox so I am familiar with setup. Client now wants to move to microk8s. Any lead would be super fantastic

I think the issue here is that you're mexing up the

flyte-core

Helm chart with values that only the

flyte-sandbox

chart can render. This tutorial guides you from the microk8s config to the Flyte installation (either flyte-binary or flyte-core)

Thanks @average-finland-92144 I got flyte running. I am doing this on my own GCP account. Got all pods in 'Running' status finally.