New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with Kong installation via Helm Chart 2.38.0 #12898
Comments
Hi, I am having the same problem. It worked perfectly one year ago with an older version of the chart. Couple of things I found:
It starts and works, but when I patch the service manually to enable the stream (this was how it was described to be done in previous versions) then, the pod is restarted and the same error is thrown again.
But it does not work. In fact I don't see anything started. What I don't understand is that if you install kong without this configuration, it does not checks for this API ... Any clue? |
After some digging, there is a If you change this to:
Fixed the problem for me. |
This issue is marked as stale because it has been open for 14 days with no activity. |
Is there an existing issue for this?
Kong version (
$ kong version
)3.6
Current Behavior
After installing Kong with the latest Helm Chart, I'm receiving the following error message:
info setup Retrying Kong admin API client call after error {"v"d"}: 0, "retries": "41/60", "error": "making HTTP request: Get "https://localhost:8444/\": dia: 0, "retries": "41/60", "error": "making HTl tcp [::1]:8444: connect: connection refused"}
The installation with Helm Chart version 2.29.0 with same values.yaml works without any problems. I've noticed there was a similar issue reported in #10334, but the PR couldn't help me with that.
The used values.yaml file.:
Expected Behavior
No response
Steps To Reproduce
helm repo add kong https://charts.konghq.com
helm repo update
helm install kong kong/kong -n kong -f values.yaml
Anything else?
No response
The text was updated successfully, but these errors were encountered: