Hey! No idea why pods are not successfully deployed, Following doc as it is https://docs.flyte.org/en/latest/deployment/gcp/manual.html#deployment-gcp-manual

Can you attempt to get the logs?

message has been deleted

@creamy-baker-21593 are you using M1 Mac ?

its ubuntu 20.4 on hp

kubectl logs -n flyte flyteadmin-<pod I'd> -c run-migrations

You may want to add -p to the command

message has been deleted

The error is that it's trying to connect to database on host "postgres".. but that doesn't sound right... Where is the db located?

db is on GCP postgressql instance

Hi @creamy-baker-21593 did these verification steps run successfully for you from the doc which uses a postgres client . “Verify connectivity to the DB from the GKE cluster.”

Hi @icy-agent-73298 What should be the output of that command? I am getting this. For both Public and Private SQL IP.

Hi @creamy-baker-21593 the instance should be accessible over the private ip and not the public ip as flyteadmin is not expected to go over the internet to connect to db. Check if you have configured the private ip correctly for the sql instance . The test is basically creating a pod on the eks cluster and making sure the eks cluster is able to connect on the private ip

Thanks, @icy-agent-73298 I am understanding this. At this point in time, the SQL and gke connectivity is successful with Public IP as a host. I have used the same Public IP to deploy helm chart in gcp-values file. It should work now? But pods are still failing

For external public IP access I suppose we would need an egress configuration which is not provided with flyte deployment . also it’s a security issue to keep a publically accessible DB. I would suggest first try with private ip to make things work and if you are ok with keeping db publically accessible then we can investigate the egress route.

Connection is failing with Private IP. For now, we can keep it DB public, and will work on security once done with successful deployment.

Not a networking expert here but i will have @high-park-82026 or someone who has tried such a setup help here. Currently the deployment guide was produced for Private IP config only