Hello
Since a few days some customers have reported that their no response was arriving to their request
Tracing back the requests they have done, we can a CD termination state on each of them.
How can I debug this ?
Thanks
Jonathan
P.S here you can see some requests with CD status
Oct 19 00:10:36 lb001 haproxy[961160]: 44.210.147.148:34960 [19/Oct/2023:00:05:54.295] kube-ingress kube-https-ingress/knode004.gladia.io 1/0/281963 6301 CD 213/37/36/17/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 92.204.243.227:2039 [19/Oct/2023:00:12:29.984] kube-ingress kube-https-ingress/knode004.gladia.io 1/0/118 4946 CD 209/36/35/17/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 44.198.171.155:7674 [19/Oct/2023:00:12:28.842] kube-ingress kube-https-ingress/knode004.gladia.io 1/1/1277 5580 – 208/35/34/16/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 18.232.73.48:59162 [19/Oct/2023:00:05:54.377] kube-ingress kube-https-ingress/knode004.gladia.io 1/0/395905 7106 CD 209/34/33/15/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 34.239.153.236:50906 [19/Oct/2023:00:05:54.276] kube-ingress kube-https-ingress/knode002.gladia.io 1/0/396112 7106 CD 208/33/32/17/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 23.23.23.6:52920 [19/Oct/2023:00:06:16.347] kube-ingress kube-https-ingress/knode002.gladia.io 1/1/374071 6301 CD 207/32/31/16/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 34.229.47.212:42698 [19/Oct/2023:00:05:54.510] kube-ingress kube-https-ingress/knode002.gladia.io 1/1/396020 7106 CD 206/31/30/15/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 44.212.43.224:59348 [19/Oct/2023:00:06:16.667] kube-ingress kube-https-ingress/knode004.gladia.io 1/1/374099 6301 CD 205/30/29/14/0 0/0
Oct 19 00:12:30 lb001 haproxy[961160]: 34.228.219.88:46300 [19/Oct/2023:00:05:54.305] kube-ingress kube-https-ingress/knode004.gladia.io 1/0/396683 7106 CD 204/29/28/13/0 0/0