Stuck with nginx ingress controller

General Discussions
1

Hello everyone,

I’m actually stuck with an ingress that I try to get working on my kubernetes cluster.
The pod is OK. I can test a curl request with 127.0.0.1 and it is working. This request is a bit long, but it is working.

If I try to send the same request through the service (from another pod), same result, it is OK.

Now I have crated an ingress to access from public. And now I have this error:

> accept: */*
> 
  0     0    0     0    0     0      0      0 --:--:--  0:00:49 --:--:--     0* HTTP/2 stream 1 was not closed cleanly before end of the underlying stream
  0     0    0     0    0     0      0      0 --:--:--  0:00:50 --:--:--     0

* Connection #0 to host xxxxx left intact

curl: (18) HTTP/2 stream 1 was not closed cleanly before end of the underlying stream
curl -v  -o res.json  0,03s user 0,03s system 0% cpu 50,348 total

Every request from outside seems to be killed exactly at 50s !

I have tried to change these annotations without any success:

    nginx.ingress.kubernetes.io/proxy-body-size: 100m
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-buffering: "on"
    nginx.ingress.kubernetes.io/proxy-buffer-size: "32k"
    nginx.ingress.kubernetes.io/proxy-buffers-number: "16"
    nginx.ingress.kubernetes.io/connection-proxy-header: "keep-alive"

I don’t know how to solve this. Any idea please ?

2

finally found the solution. It was a firewall timeout issue …