From 7339db529de5c05a664abad54189095ec75deb22 Mon Sep 17 00:00:00 2001
From: Chris Kim <30601846+Oats87@users.noreply.github.com>
Date: Mon, 3 Dec 2018 17:18:04 -0800
Subject: [PATCH] Add -n ingress-nginx to the create secret dry-run command

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.
---
 .../en/config-options/add-ons/ingress-controllers/_index.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md b/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
index 6865e1a535c..dd9df942ddf 100644
--- a/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
+++ b/content/rke/v0.1.x/en/config-options/add-ons/ingress-controllers/_index.md
@@ -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: