Closed A7exSchin closed 1 month ago
Hi @A7exSchin 👋
You should get the new CRDs (KongVault
specifically) installed when installing kong/ingress
0.13.1.
I just checked it by running
helm upgrade --install --create-namespace -n kong kong kong/ingress --version v0.13.1
and after deleting the CRD before the installation, I do get it installed with the chart.
Not sure why that wouldn't work. Can you share the values.yaml
?
You can always disable the vault controller if you don't use it
controller:
ingressController:
env:
enable_controller_kong_vault: "false"
As for the second error, this is related to an upstream issue https://github.com/kubernetes-sigs/controller-runtime/issues/2723 which is still open.
Hi @pmalek !
The quick response is very much appreciated. The last code block you see is the values.yaml for the controller ressource (as I am using the ingress chart, I only included the nested values.yaml for the nested chart and excluded the part for the gateway).
I will try to disable the kong vault.
We are currently deploying this helm chart via terraform so I cannot really say why it is not creating the CRDs properly. Will try to investigate
Hi again @pmalek !
We disabled the KongVault according to your suggested fix and that worked! Thanks!
However, I am not sure why the Helm Deployment Process is not correctly deploying the CRDs
Hi there!
We recently updated our
kong/ingress
chart from0.10.1
to0.13.1
. This in turn updated thekong/kong
chart form2.30.0
to2.39.3
.I checked the values and it did not look like anything affecting our deployment was changed. However, the ingress controller restarts every 3 minutes with multiple errors, which are not really indicative of what is wrong.
First error message block:
We are not using KongVaults at all in our deployment.
This is the second error log:
This is the code used to deploy the controller inside the
helm/ingress
chart: