You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, currently, I am using the 2.46.0 version of the chart, and the ingress controller container of every pod always needs to restart a few times before it finally becomes healthy. Upon checking the logs, I saw this line.
Error: unable to build kong api client(s): client not ready: making HTTP request: Get "https://localhost:8444/status": dial tcp 127.0.0.1:8444: connect: connection refused
I tried to delay the initial readiness probe but to no avail. I think it was caused by the container exiting due to the error. Is this expected? Is there a way to delay the initial HTTP request to the proxy container? Thank you 🙏
The text was updated successfully, but these errors were encountered:
Hi, currently, I am using the 2.46.0 version of the chart, and the ingress controller container of every pod always needs to restart a few times before it finally becomes healthy. Upon checking the logs, I saw this line.
Error: unable to build kong api client(s): client not ready: making HTTP request: Get "https://localhost:8444/status": dial tcp 127.0.0.1:8444: connect: connection refused
I tried to delay the initial readiness probe but to no avail. I think it was caused by the container exiting due to the error. Is this expected? Is there a way to delay the initial HTTP request to the proxy container? Thank you 🙏
The text was updated successfully, but these errors were encountered: