Gents, I am experiencing an issue here and I am sure I am just missing something really small. I am in the process of test driving kong in my dev Kubernetes cluster. Kong configuration documentation actually explains that postgres and cassandra are the two databases supported. This chart actually h…

Honestly, there is not much of any logging and that has been the challenging. It is like shooting in the dark. This is all I see Error from server (BadRequest): container "kong-migrations" in pod "kong-kong-init-migrations-m5grv" is waiting to start: PodInitializing

That is correct, a user and database is already created and that user is the owner of the database kong is supposed to use.

That job runs a basic init to confirm it can establish a connection: Kong/charts/blob/master/charts/kong/templates/_helpers.tpl#L551-L558 {{- define "kong.wait-for-postgres" -}} - name: wait-for-postgres image: "{{ .Values.waitImage.repository }}:{{ .Values.waitImage.tag }}" imagePull…

Here is what kubectl describe POD_NAME gives me, there seem to be no error there. Name: kong-kong-init-migrations-dbblz Namespace: gateway Priority: 0 Node: worker3/192.168.1.23 Start Time: Mon, 20 Apr 2020 16:48:16 -0400 Labels: app.kubernetes.io/componen…

I cannot get logs for a container if the pod is not initialized properly.

I honestly can say something just does not look right here. For what it is worth I am using version 1.5.0 of the helm chart. I also noticed that the batch job command uses [ "/bin/sh", "-c", "kong migrations up" ] whereas the docker documentation mandates it to be [ "/bin/sh", "-c", "kong migrations…

Can someone please share with me a values.yaml file that works for chart version 1.5.0, this chart uses kong version 2.0.3. @traines . Thanks in advance.

You can get logs for initContainers, it’s just that the logs command won’t do it automatically. The container has it be specified explicitly, kubectl logs JOB_POD -c wait-for-postgres Can you provide output from that?

[image] bsakweson: Honestly, there is not much of any logging and that has been the challenge. It is like shooting in the dark. This is all I see Error from server (BadRequest): container "kong-migrations" in pod "kong-kong-init-migrations-m5grv" is waiting to start: PodInitializing I provide…

Kong Helm Chart and External Postgres database

Questions

hbagdi April 22, 2020, 11:18pm 8

ping @traines …

Topic		Replies	Views
Kong-migrate pod is in the CrashLoopBackOff when pulling Postgres image from a private repo using HELM Questions kubernetes	0	1376	February 21, 2022
/usr/local/share/lua/5.1/kong/init.lua:337: in function 'init' Questions	7	4649	June 28, 2019
Installing kong-ingress-controller to manage ingress on kubernetes Announcements kubernetes	3	5053	March 14, 2019
Kong kubernetes pod does not start after system restart kubernetes , kong-gateway	17	5756	November 10, 2023
Kong container can't reach the external host postgres Questions kubernetes	2	2327	September 5, 2019

Kong Helm Chart and External Postgres database

Related topics