You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering a problem deploying Kong with Helm chart on AWS EKS while using PostgreSQL 16 with AWS RDS.
I'm using chats version kong/kong 2.41.1 and when the pods to EKS the deployment fails, displaying the following error message:
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:115: [PostgreSQL error] failed to insert cluster lock: unexpected result
stack traceback:
[C]: infunction'error'
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:115: infunction'up'
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:204: infunction'cmd_exec'
...
However, this issue does not occur when using PostgreSQL 13.3. The problem seems specific to PostgreSQL versions higher than 14.
Actual Behavior:
Deploy the Kong Helm chart using PostgreSQL 16 as the database.
Connection with AWS RDS, exists because create 2 tables and insert values on table lock.
Observe the error during the migration phase: [PostgreSQL error] failed to insert cluster lock: unexpected result.
The migration status command (kong migrations status) outputs the following:
Configurations in migration:
migrations:
preUpgrade: truepostUpgrade: true
The text was updated successfully, but these errors were encountered:
I'm encountering a problem deploying Kong with Helm chart on AWS EKS while using PostgreSQL 16 with AWS RDS.
I'm using chats version kong/kong 2.41.1 and when the pods to EKS the deployment fails, displaying the following error message:
However, this issue does not occur when using PostgreSQL 13.3. The problem seems specific to PostgreSQL versions higher than 14.
Actual Behavior:
Deploy the Kong Helm chart using PostgreSQL 16 as the database.
Connection with AWS RDS, exists because create 2 tables and insert values on table lock.
Observe the error during the migration phase: [PostgreSQL error] failed to insert cluster lock: unexpected result.
The migration status command (
kong migrations status
) outputs the following:Configurations in migration:
The text was updated successfully, but these errors were encountered: