Istio version: 1.0.2 Kubernetes version: 1.11.6 CNI: Calico. Running on AWS EC2
My istio-proxy log both for the application and the istio ingress-gateway show HTTP 0 responses.
[2019-02-22T14:17:26.491Z] "POST /logs HTTP/1.1" 0 - 416 0 0 - "106.203.21.132, 100.119.170.64" "-" "73df9db4-56c5-91eb-be01-032d213963bc" "blah.net" "127.0.0.1:4001"
Following envoy metrics spike up when the application gives the HTTP 0 response code:
envoy_http_100_101_221_198_4001_downstream_cx_destroy_remote
envoy_http_100_101_221_198_4001_downstream_cx_destroy_active_rq
envoy_http_100_101_221_198_4001_downstream_cx_destroy_remote_active_rq
envoy_http_100_101_221_198_4001_downstream_cx_length_ms
-
Based on this, at what stage the connection is terminated?
Client -> Ingress gateway or Ingress gateway -> Application -
What could cause the connection termination? Are we hitting some limit? Config error? Issue with the request?