Is this a BUG or FEATURE REQUEST?:
Bug
Did you review existing epics or issues to identify if this already being worked on?
Searched for all issues with labels: ingress fault (delay|arbort)
Bug:
Y
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
How to reproduce it:
just follow the documentation about ingress.
note that I deployed httpbin application and service in the default namespace. The ingress also is in default. I tried in a dedicated namespace and the problem remains.
Is this a BUG or FEATURE REQUEST?: Bug Did you review existing epics or issues to identify if this already being worked on? Searched for all issues with labels: ingress fault (delay|arbort) Bug: Y
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
Istio installation procedure from https://istio.io/docs/setup/kubernetes/quick-start.html
Is Istio Auth enabled or not ? istio.yaml ; (no auth) not using automatic kube proxy injector; (manual kube inject)
What happened: following the documentation for ingress here: https://istio.io/docs/tasks/traffic-management/ingress.html the validation step 3 does not return the expected result:
What you expected to happen:
the expected result is described in the ingress documentation ( https://istio.io/docs/tasks/traffic-management/ingress.html , section Verifying ingress bloc 3
How to reproduce it: just follow the documentation about ingress.
note that I deployed httpbin application and service in the default namespace. The ingress also is in default. I tried in a dedicated namespace and the problem remains.
References I could find about this issue: https://github.com/istio/istio.github.io/pull/239/files https://github.com/istio/issues/issues/87#issuecomment-335523643