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

Merge pull request #3762 from rush2sk8/patch-1

Browse Source 
Update _index.md
This commit is contained in:
Billy Tat
2022-01-25 14:12:22 -08:00
committed by GitHub
parent 5f2b72d5be df9a7f5ebe
commit 33f16d36c8
3 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/_index.md
+8 -2
View File
@@ -131,7 +131,12 @@ deployment "rancher" successfully rolled out
This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA. This configuration uses HTTP validation (`HTTP-01`) so the load balancer must have a public DNS record and be accessible from the internet.
- Set `hostname` to the public DNS record, set `ingress.tls.source` to `letsEncrypt` and `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices)
In the following command,
- Set `hostname` to the public DNS record that resolves to your load balancer.
- Set `ingress.tls.source` to `letsEncrypt`.
- Set `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices).
- Set `letsEncrypt.ingress.class` to whatever your ingress controller is, e.g., `traefik`, `nginx`, `haproxy`, etc.
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command.
```
@@ -140,7 +145,8 @@ helm install rancher-<CHART_REPO>/rancher \
--namespace cattle-system \
--set hostname=rancher.my.org \
--set ingress.tls.source=letsEncrypt \
--set letsEncrypt.email=me@example.org
--set letsEncrypt.email=me@example.org \
--set letsEncrypt.ingress.class=nginx
```
Wait for Rancher to be rolled out:
content/rancher/v2.5/en/installation/install-rancher-on-k8s/_index.md
+3 -1
View File
@@ -190,7 +190,7 @@ deployment "rancher" successfully rolled out
This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA.
>**Note:**: You need to have port 80 open as the HTTP-01 challenge can only be done on port 80.
>**Note:** You need to have port 80 open as the HTTP-01 challenge can only be done on port 80.
In the following command,
@@ -198,6 +198,7 @@ In the following command,
- Set `replicas` to the number of replicas to use for the Rancher Deployment. This defaults to 3; if you have less than 3 nodes in your cluster you should reduce it accordingly.
- Set `ingress.tls.source` to `letsEncrypt`.
- Set `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices).
- Set `letsEncrypt.ingress.class` to whatever your ingress controller is, e.g., `traefik`, `nginx`, `haproxy`, etc.
- To install a specific Rancher version, use the `--version` flag, example: `--version 2.3.6`.
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command.
@@ -208,6 +209,7 @@ helm install rancher rancher-<CHART_REPO>/rancher \
--set replicas=3 \
--set ingress.tls.source=letsEncrypt \
--set letsEncrypt.email=me@example.org
--set letsEncrypt.ingress.class=nginx
```
Wait for Rancher to be rolled out:
content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md
+3 -1
View File
@@ -181,7 +181,7 @@ deployment "rancher" successfully rolled out
This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA.
>**Note:**: You need to have port 80 open as the HTTP-01 challenge can only be done on port 80.
>**Note:** You need to have port 80 open as the HTTP-01 challenge can only be done on port 80.
In the following command,
@@ -189,6 +189,7 @@ In the following command,
- Set the `bootstrapPassword` to something unique for the `admin` user.
- `ingress.tls.source` is set to `letsEncrypt`
- `letsEncrypt.email` is set to the email address used for communication about your certificate (for example, expiry notices)
- Set `letsEncrypt.ingress.class` to whatever your ingress controller is, e.g., `traefik`, `nginx`, `haproxy`, etc.
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command.
```
@@ -198,6 +199,7 @@ helm install rancher rancher-<CHART_REPO>/rancher \
--set bootstrapPassword=admin \
--set ingress.tls.source=letsEncrypt \
--set letsEncrypt.email=me@example.org
--set letsEncrypt.ingress.class=nginx
```
Wait for Rancher to be rolled out: