Closed ngingihy closed 2 years ago
Hi @ngingihy,
Is the image privateRegistry.com/repo1/kong:latest
a copy of bitnami/kong
or is it a customized image?
The bitnami/kong
image includes the logic to migrate/bootstrap the PostgreSQL database, which I think is not being executed in this case.
Below is the logic included in the bitnami/docker image, which based on the value of KONG_MIGRATE ('yes' in the kong-migrate job) will run the command kong migrations bootstrap
:
https://github.com/bitnami/bitnami-docker-kong/blob/769409663f01e363f2e951e54a862b83855b5be9/2/debian-10/rootfs/opt/bitnami/scripts/libkong.sh#L136-L166
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/kong
What steps will reproduce the bug?
1)I'm provisioning a namespace in a cluster, added the repo, trying to install kong chart. 2)In the values.yml file, pulling all the images from a private repo. It successfully pull all the images. 3) The installation fails due to
when i try to check the pods running, i see
when I check the events on my cluster, I see
when i check the kong-migrate pod logs, i see
[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.
I already have pvc, kubectl get PVC
I'm trying to figure out what i'm missing here
Are you using any custom parameters or values?
These is my values.yaml file
What is the expected behavior?
No response
What do you see instead?
The installation times out and from the kong-migrate pod, i get this error
[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.
Additional information
No response