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

Update guides to use official Charts repository

Browse Source
This commit is contained in:
Roy Hvaara 2018-02-26 21:39:41 +01:00
parent 0a0a2f3b13
commit 87fa7b170b
No known key found for this signature in database
GPG Key ID: 86178E27A70076C7
2 changed files with 4 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/user-guides/deploying.md
View File

@ -21,29 +21,19 @@ RBAC can be found [here](https://github.com/kubernetes/helm/blob/master/docs/rba
### Step 1 - deploying cert-manager
To deploy the latest version of cert-manager using Helm you will first need to
clone this repository:
```bash
$ git clone https://github.com/jetstack/cert-manager
$ cd cert-manager
# check out the latest release tag to ensure we use a supported version of cert-manager
$ git checkout v0.2.3
```
We can then go ahead and install the bundled chart:
The latest version of cert-manager can be installed from the official Charts repository for Helm:
```bash
$ helm install \
--name cert-manager \
--namespace kube-system \
contrib/charts/cert-manager
stable/cert-manager
```
> **NOTE**: if your cluster does not use RBAC (Role Based Access Control), you should add `--set rbac.enabled=false` when running your `helm install` command.
The default cert-manager configuration is good for the majority of users, but a
full list of the available options can be found in the [Helm chart README](https://github.com/jetstack/cert-manager/blob/master/contrib/charts/cert-manager/README.md).
full list of the available options can be found in the [Helm chart README](https://github.com/kubernetes/charts/blob/master/stable/cert-manager/README.md).
Next, you will need to configure cert-manager with Issuers and ClusterIssuers.
These represent a 'source' for x509 certificates and will be used later on to

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

@ -202,15 +202,11 @@ ClusterIssuer `letsencrypt-staging` (as above), run:
```bash
helm upgrade \
cert-manager \
./contrib/charts/cert-manager \
stable/cert-manager \
--namespace kube-system \
--set ingressShim.extraArgs='{--default-issuer-name=letsencrypt-staging,--default-issuer-kind=ClusterIssuer}'
```
If you get an error like: `Error: path "./contrib/charts/cert-manager" not found`,
ensure you have cloned the cert-manager repository and you are in the root of
the repository.
You should see the cert-manager pod be re-created, and once started it should
automatically create Certificate resources for all of your ingresses that
previously had kube-lego enabled.