DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #1157 from mbssaiakhil/patch-9

Browse source 
Fix minor typos in Prerequisites
This commit is contained in:
Manuel Alejandro de Brito Fontes 2017-08-16 19:00:40 -03:00 committed by GitHub
commit 2af4791476
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
examples/PREREQUISITES.md
View file

@ -40,7 +40,7 @@ secret "tls-secret" created
You can act as your very own CA, or use an existing one. As an exercise / learning, we're going to generate our You can act as your very own CA, or use an existing one. As an exercise / learning, we're going to generate our
own CA, and also generate a client certificate. own CA, and also generate a client certificate.
These instructions are based in CoreOS OpenSSL [instructions](https://coreos.com/kubernetes/docs/latest/openssl.html) These instructions are based on CoreOS OpenSSL [instructions](https://coreos.com/kubernetes/docs/latest/openssl.html)
### Generating a CA ### Generating a CA
@ -72,7 +72,7 @@ This will generate two files: A private key (ca.key) and a public key (ca.crt).
The ca.crt can be used later in the step of creation of CA authentication secret. The ca.crt can be used later in the step of creation of CA authentication secret.
### Generating the client certificate ### Generating the client certificate
The following steps generates a client certificate signed by the CA generated above. This client can be The following steps generate a client certificate signed by the CA generated above. This client can be
used to authenticate in a tls-auth configured ingress. used to authenticate in a tls-auth configured ingress.
First, we need to generate an 'openssl.cnf' file that will be used while signing the keys: First, we need to generate an 'openssl.cnf' file that will be used while signing the keys: