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

bug with new certs getting picked up (#1987)

This commit is contained in:
Gregory Hanson 2018-07-26 10:45:22 -05:00 committed by Shriram Rajagopalan
parent fa59263b52
commit 59e10c2495
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -290,6 +290,12 @@ they have valid values, according to the output of the following commands:
$ kubectl logs -n istio-system -l istio=ingressgateway
{{< /text >}}
1. If the secret was created but the keys were not mounted, kill the ingress gateway pod and force it to reload certs:
{{< text bash >}}
$ kubectl delete pod -n istio-system -l istio=ingressgateway
{{< /text >}}
1. For macOS users, verify that you use _curl_ compiled with the [LibreSSL](http://www.libressl.org) library, as
described in the [Before you begin](#before-you-begin) section.
@ -312,6 +318,12 @@ In addition to the steps in the previous section, perform the following:
Subject: C=US, ST=Denial, L=Springfield, O=Dis, CN=httpbin.example.com
{{< /text >}}
1. If the secret was created but the keys were not mounted, kill the ingress gateway pod and force it to reload certs:
{{< text bash >}}
$ kubectl delete pod -n istio-system -l istio=ingressgateway
{{< /text >}}
## Cleanup
1. Delete the `Gateway` configuration, the `VirtualService`, and the secrets: