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

fail with 503 instead of 000 for injected-app (#3157) 

* fail with 503 instead of 000 for injected-app

As a bad destination rule is set to disable client side mTLS and receiving side is mTLS enabled. At this point, Running the curl command between sidecar injected Istio services  all requests will fail with a 503 error code as the client side is still using plain-text.
This commit is contained in:
idouba 2019-03-07 00:48:20 +08:00 committed by Martin Taillefer
parent da77bb2bb5
commit f02b763382
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/docs/tasks/security/mutual-tls/index.md
View File

@ -127,12 +127,11 @@ HOST:PORT STATUS SERVER CLIENT AU
httpbin.default.svc.cluster.local:8000 CONFLICT mTLS HTTP default/ bad-rule/default
{{< /text >}}
You can also confirm that requests from `sleep` to `httpbin` are now failed:
You can also confirm that requests from `sleep` to `httpbin` are now failing:
{{< text bash >}}
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c sleep -- curl httpbin:8000/headers -o /dev/null -s -w '%{http_code}\n'
000
command terminated with exit code 56
503
{{< /text >}}
Before you continue, remove the bad destination rule to make mutual TLS work again with the following command: