weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #376 from jetstack/munnerz-patch-1

Browse Source 
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Clarify ClusterIssuer resource namespace

**What this PR does / why we need it**:

Clarify ClusterIssuer resource namespace in the migrating from kube lego guide

**Release note**:
```release-note
NONE
```
This commit is contained in:
jetstack-ci-bot 2018-03-12 10:28:16 +00:00 committed by GitHub
commit cfa13a02df
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/user-guides/migrating-from-kube-lego.md
View File

@ -86,8 +86,10 @@ more relevant to cert-manager. For the rest of this guide, we'll assume you
chose `letsencrypt-private-key`.
Once done, we need to create this new resource in the `kube-system` namespace.
This is where cert-manager looks for supporting resources for ClusterIssuers
by default:
By default, cert-manager stores supporting resources for ClusterIssuers in the
namespace that it is running in, and we used `kube-system` when deploying
cert-manager above. You should change this if you have deployed cert-manager into
a different namespace.
```bash
$ kubectl create \