public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add -n ingress-nginx to the create secret dry-run command

Browse Source 
Currently, if you take the contents of `ingress-default-cert.yaml` and paste it into your RKE config, the secret will get created in the namespace `default` which is not desired behavior. By specifying `-n ingress-nginx`, the secret will be created in the correct namespace.
This commit is contained in:
Chris Kim
2018-12-03 17:54:53 -08:00
committed by Denise
parent a8af0c46a2
commit 7339db529d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
+1 -1
View File
@@ -67,7 +67,7 @@ Setting up a default certificate is especially helpful in environments where a w
2. Generate a Kubernetes secret from your PEM encoded certificate with the following command, substituting your certificate for `mycert.cert` and `mycert.key`.
```
kubectl create secret tls ingress-default-cert --cert=mycert.cert --key=mycert.key -o yaml --dry-run=true > ingress-default-cert.yaml
kubectl -n ingress-nginx create secret tls ingress-default-cert --cert=mycert.cert --key=mycert.key -o yaml --dry-run=true > ingress-default-cert.yaml
```
3. Include the contents of `ingress-default-cert.yml` inline with your RKE `cluster.yml` file. For example: