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

Clarify ClusterIssuer resource namespace

Browse Source
This commit is contained in:
James Munnelly 2018-03-02 11:12:11 +00:00 committed by GitHub
parent 24f0bbe1f3
commit 4e262ee1d7
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`. chose `letsencrypt-private-key`.
Once done, we need to create this new resource in the `kube-system` namespace. 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, cert-manager stores supporting resources for ClusterIssuer's in the
by default: 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 ```bash
$ kubectl create \ $ kubectl create \