HarryandKubernetes Prow Robot
d2cd8421fa
* [stable/kong] consolidate all rbac resources into a single file - Simplify and reduce number of ifs in our helm chart to reduce maintainence burden Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] move all custom resources into a single file Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] remove podDistruption budget for ingressController Ingress Controller has been consolidated into the Kong pod itself now so this policy is not needed anymore. Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] refactor wait-for-postgres container into helpers for de-duplication Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] refactor env section of the deployment into a helper In the next commit, we will use this same env section for the migration containers as well to ensure consistency in Kong's configuration across different pods. Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] use kong.final_env for migration containers This ensures that the exact same configuration for kong is used across containers of all types. Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] wait-for-postgres to be available Previously, if the Postgres instance was managed externally, eg, like an RDS instance, then the chart would fail to wait for it. The migrations eventually succeeded but if the pod fails while connecting to Postgres, it is more helpful as it highlights an issue with network itself. Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] use a hard-coded name for the container name This allows us to have determisintic container names and makes writing scripts easier. The name of the pod and deployment are still generated by Helm. Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] bump up Postgresql sub-chart to 8.1.2 Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] write changelog and bump chart for 0.33 Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * fix: remove installCRDs since it is present twice Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] add content of FAQ doc Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] re-orgnize values.yaml Signed-off-by: Harry Bagdi <harrybagdi@gmail.com> * [stable/kong] fix language in the FAQ Signed-off-by: Harry Bagdi <harrybagdi@gmail.com>
1.3 KiB
Frequently Asked Questions (FAQs)
Kong fails to start after helm upgrade when Postgres is used. What do I do?
You may be running into this issue: https://github.com/helm/charts/issues/12575. This issue is caused due to: https://github.com/helm/helm/issues/3053.
The problem that happens is that Postgres database has the old password but the new secret has a different password, which is used by Kong, and password based authentication fails.
The solution to the problem is to specify a password to the postgresql chart.
This is to ensure that the password is not generated randomly but is set to
the same one that is user-provided on each upgrade.
Kong fails to start on a fresh installation with Postgres. What do I do?
Please make sure that there is no PersistentVolumes present from a previous
release. If there are, it can lead to data or passwords being out of sync
and result in connection issues.
A simple way to find out is to use the following command:
kubectl get pv -n <your-namespace>
And then based on the AGE column, determine if you have an old volume.
If you do, then please delete the release, delete the volume, and then
do a fresh installation. PersistentVolumes can remain in the cluster even if
you delete the namespace itself (the namespace in which they were present).