istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add ingress troubleshooting section (#3410) 

* add ingress troubleshooting section

* it does not arrive to the Istio -> it does not arrive to the ingress gateway

* fix a link

* remove checking the log since access log will be removed in 1.1

* you have no other Kubernetes Ingress resources -> you have no Kubernetes Ingress resources
This commit is contained in:
Vadim Eisenberg 2019-03-06 18:59:38 +02:00 committed by Martin Taillefer
parent f02b763382
commit e8a799f919
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
content/docs/tasks/traffic-management/ingress/index.md
View File

@ -266,6 +266,31 @@ available for edge services.
In the preceding steps, you created a service inside the service mesh
and exposed an HTTP endpoint of the service to external traffic.
## Troubleshooting
1. Inspect the values of the `INGRESS_HOST` and `INGRESS_PORT` environment variables. Make sure
they have valid values, according to the output of the following commands:
{{< text bash >}}
$ kubectl get svc -n istio-system
$ echo INGRESS_HOST=$INGRESS_HOST, INGRESS_PORT=$INGRESS_PORT
{{< /text >}}
1. Check that you have no other Istio ingress gateways defined on the same port:
{{< text bash >}}
$ kubectl get gateway --all-namespaces
{{< /text >}}
1. Check that you have no Kubernetes Ingress resources defined on the same IP and port:
{{< text bash >}}
$ kubectl get ingress --all-namespaces
{{< /text >}}
1. If you have an external load balancer and it does not work for you, try to access the gateway using the service's
[node port](/docs/tasks/traffic-management/ingress/#determining-the-ingress-ip-and-ports-when-using-a-node-port).
## Cleanup
Delete the `Gateway` and `VirtualService` configuration, and shutdown the [httpbin]({{< github_tree >}}/samples/httpbin) service: