Closed Rockyjr-git closed 1 month ago
Please share the values.yaml that you've used to deploy. Have you used kong
chart? You can configure this port using https://github.com/Kong/charts/blob/fe3c070b614dea6db0ed6517871c3dfdc75b0516/charts/kong/values.yaml#L317 proxy.tls.containerPort
@pmalek Thanks for quick response, Tired the above changes already. Results the kong pods in crashloopbackoff
I have just tried this with the latest version of the chart and it worked fine. We'll need a bit more information than just those screenshots to asses.
Please provide
helm ls -A
ideally)kubectl describe
of failing podsPlease find the attached logs and screenshot kong-values.zip
To get the logs please execute:
kubectl logs -n <NAMESPACE> deployment/<KONG_DEPLOYMENT_NAME>
and attach the output. The readiness probes seems to be failing for some reason.
Please note: your values.yaml looks like a copy paste from https://github.com/Kong/charts/blob/main/charts/kong/values.yaml with several fields changed. This is not how Helm values should be used. You should only specify the entries to you intend to override on top of the base values.yaml provided by Kong (https://github.com/Kong/charts/blob/main/charts/kong/values.yaml).
We are using same values.yaml by overriding Downloads.zip the required values. Please find the attached values.yaml. Also logs of proxy and controller pods are attached.
Looking at the values.yaml
I can still see that it contains almost all of the defaults from https://github.com/Kong/charts/blob/main/charts/kong/values.yaml. You should only specify the values that you're actually overriding. Do not copy paste all and then change those that you want to amend.
Looking at the proxy logs I can see
ERROR: ld.so: object '/opt/dynatrace/oneagent-paas/agent/lib64/liboneagentproc.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
which indicates that your environment has some broken LD_PRELOAD
configuration that prevents Kong from starting. Please fix that and then we can take a look again.
Is there an existing issue for this?
Current Behavior
Port 8443 is used
Expected Behavior
Replace port 8443 with other ports
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
Kong Ingress controller is deployed using Helm chart, Since Port 8443 is being used by other application. I need to replace that Port with other Ports.