-
I am using google managed postgrsql with kong on GKE. And my migration pod seems to be stuck and not doing it's job. I have install kong with helm using the below values. image:
repository: kong
tag: "3.5"
env:
prefix: /kong_prefix/
database: postgres
admin_gui_api_url:
admin_gui_url:
pg_host:
pg_user:
pg_password:
pg_database:
admin:
enabled: true
type: LoadBalancer
http:
enabled: true
servicePort: 8001
containerPort: 8001
postgresql:
enabled: false
ingressController:
enabled: false
manager:
enabled: true
type: LoadBalancer
http:
enabled: true
servicePort: 8002
containerPort: 8002
migrations:
enabled: true
postUpgrade: true
preUpgrade: true NAME READY STATUS RESTARTS AGE
my-kong-kong-69fb74bbdd-wh9tq 0/1 Init:1/2 0 8m2s
my-kong-kong-init-migrations-gmw5q 0/1 CrashLoopBackOff 4 (80s ago) 8m2s # pod logs
Error: [PostgreSQL error] failed to retrieve PostgreSQL server_version_num: timeout |
Beta Was this translation helpful? Give feedback.
Answered by
hashaaamm
Jun 21, 2024
Replies: 1 comment 1 reply
-
The error usually indicates that postgres could not be reached. Can you check that you're able to authenticate to postgres? You probably redacted the values but just checking. Did you populate these values?
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you. It's solved. The issue was with google managed postgrsql. It doesn't allow direct access and requires additional stuff.