Nick_Duan
Nick_Duan
but i run with docker it's ok: ```bash docker run -it kong:3.5 bash # Enter the container export KONG_DATABASE=off ./docker-entrypoint.sh kong docker-start --vv ``` get normal log ```bash 2024/01/25 03:24:27...
> ```diff > + local _, err = assert(prepare_prefix(conf, nil, true)) > ``` This may be caused by the running permissions, maybe I found what the problem exactly is, So...
> You can add the suggested argument to the proxy container. We don't expose args in values.yaml (most everything is controlled through environment variables instead, but the verbose flags aren't),...
this is my debug information: ```yaml Release "kong" has been upgraded. Happy Helming! NAME: kong LAST DEPLOYED: Fri Jan 19 15:04:03 2024 NAMESPACE: kong STATUS: deployed REVISION: 7 TEST SUITE:...
> > after add args, run `helm -n kong install kong kong/kong -f ./charts/config.yaml --debug` i got this in `proxy` container(args=`["kong", "docker-start", "--vv"]`): > > ```shell > > Error: >...
And anybody knows why `ingress-controller` container get this. ```bash time="2024-01-12T10:51:41Z" level=info msg="Retrying kong admin api client call after error" error="making HTTP request: Get \"http://localhost:8001/\": dial tcp [::1]:8001: connect: connection refused"...
I found this issue: https://github.com/Kong/charts/issues/526, And set envs as @brennoo said, but it's useless for me. 
> hey @NICK-DUAN, > > It seems you need to set `admin_listen` port to 8444, check the admin port here [#983 (comment)](https://github.com/Kong/charts/issues/983#issuecomment-1899906354) I install `kong/kong`, and I get a service...
new `custom-values.yaml` ```yaml proxy: type: ClusterIP env: admin_listen: "127.0.0.1:8444 ssl" ingressController: env: kong_admin_init_retries: 5 kong_admin_init_retry_delay: "20s" ingressClass: "testkong" admin: enabled: true tls: enabled: true type: ClusterIP containerSecurityContext: {} replicaCount: 1...