Installing Kong in Kubernetes I got this errors in log
[warn] 1#0: the “user” directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:7
nginx: [warn] the “user” directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/kong/nginx.conf:7
2025/09/08 14:30:23 [error] 1#0: init_by_lua error: /usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:16: Database needs bootstrapping or is older than Kong 1.0.
To start a new installation from scratch, run ‘kong migrations bootstrap’.
To migrate from a version older than 1.0, migrated to Kong 1.5.0 first.
If you still have ‘apis’ entities, you can convert them to Routes and Services
using the ‘kong migrations migrate-apis’ command in Kong 1.5.0.
stack traceback:
[C]: in function ‘error’
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:16: in function ‘check_state’
/usr/local/share/lua/5.1/kong/init.lua:668: in function ‘init’
init_by_lua(nginx-kong.conf:44):3: in main chunk
nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:16: Database needs bootstrapping or is older than Kong 1.0
But my version of DB is “PostgreSQL 17.5 on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit”
Edit:
I have tried to disable migration. (I do not understand why migration would be useful for clean install.)
I have set migrations preUpgrade/postUpgrade: false
Now I get this:
Normal Pulled 4m43s kubelet Successfully pulled image “kong:3.9” in 15.233s (15.233s including waiting). Image size: 120417792 bytes.
Warning Unhealthy 4m38s kubelet Liveness probe failed: Get “http://192.168.xxx.xxx:8100/status”: dial tcp 192.168.xxx.xxx:8100: connect: connection refused
Warning Unhealthy 4m38s kubelet Readiness probe failed: Get “http://192.168.xxx.xxx:8100/status/ready”: dial tcp 192.168.xxx.xxx:8100: connect: connection refused
Normal Created 3m39s (x4 over 4m43s) kubelet Created container: kong
Normal Started 3m39s (x4 over 4m43s) kubelet Started container kong
Warning BackOff 3m3s (x9 over 4m32s) kubelet Back-off restarting failed container kong in pod mykong-kong-gateway-547c586b97-86wnj_nczi-ope-kong(56a85718-9851-4774-946e-57723c387cf1)