mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-24 20:18:18 +00:00
note format and search
This commit is contained in:
lvuch
@@ -28,6 +28,6 @@ kubectl create clusterrolebinding tiller \
|
||||
helm init --service-account tiller
|
||||
```
|
||||
|
||||
> NOTE: This `tiller` install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.
|
||||
> **NOTE:** This `tiller` install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.
|
||||
|
||||
### [Next: Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha//helm-rancher/)
|
||||
@@ -33,9 +33,9 @@ Rancher server is designed to be "secure by default" and requires SSL/TLS config
|
||||
|
||||
There are three options for the source of the certificate.
|
||||
|
||||
* `rancher` - (Default) Use Rancher generated CA/Certificates.
|
||||
* `letsEncrypt` - Use [LetsEncrypt](https://letsencrypt.org/) to issue a cert.
|
||||
* `secret` - Configure a Kubernetes Secret with your certificate files.
|
||||
1. `rancher` - (Default) Use Rancher generated CA/Certificates.
|
||||
2. `letsEncrypt` - Use [LetsEncrypt](https://letsencrypt.org/) to issue a cert.
|
||||
3. `secret` - Configure a Kubernetes Secret with your certificate files.
|
||||
|
||||
<br\>
|
||||
|
||||
@@ -71,11 +71,11 @@ helm install rancher-stable/rancher \
|
||||
|
||||
Create Kubernetes Secrets from your own certificates for Rancher to use.
|
||||
|
||||
> NOTE: The common name for the cert will need to match the `hostname` option or the ingress controller will fail to provision the site for Rancher.
|
||||
> **NOTE:** The common name for the cert will need to match the `hostname` option or the ingress controller will fail to provision the site for Rancher.
|
||||
|
||||
Set `hostname` and `ingress.tls.source=secret`
|
||||
|
||||
> NOTE: If you are using a Private CA signed cert, add `--set privateCA=true`
|
||||
> **NOTE:** If you are using a Private CA signed cert, add `--set privateCA=true`
|
||||
|
||||
```
|
||||
helm install rancher-stable/rancher \
|
||||
|
||||
@@ -74,11 +74,11 @@ Add the `rancherImage` to point to your private registry image and `imagePullSec
|
||||
|
||||
If you wish to terminate the SSL/TLS on a load-balancer external to the Rancher cluster (ingress), use the `--tls=external` option and point your load balancer at port http 80 on all of the rancher cluster nodes.
|
||||
|
||||
> NOTE: If you are using a Private CA signed cert, add `--set privateCA=true` and see [Adding TLS Secrets - Private CA Signed - Additional Steps]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/#private-ca-signed---additional-steps) to add the CA cert for Rancher.
|
||||
> **NOTE:** If you are using a Private CA signed cert, add `--set privateCA=true` and see [Adding TLS Secrets - Private CA Signed - Additional Steps]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/#private-ca-signed---additional-steps) to add the CA cert for Rancher.
|
||||
|
||||
Your load balancer must support long lived websocket connections and will need to insert proxy headers so Rancher can route links correctly.
|
||||
|
||||
> NOTE: The `tls=external` option will expose the Rancher interface on http port 80. Clients that are allowed to connect directly to the Rancher cluster will not be encrypted. We recommend that you restrict direct access at the network level to just your load balancer.
|
||||
> **NOTE:** The `tls=external` option will expose the Rancher interface on http port 80. Clients that are allowed to connect directly to the Rancher cluster will not be encrypted. We recommend that you restrict direct access at the network level to just your load balancer.
|
||||
|
||||
#### Required headers
|
||||
|
||||
|
||||
@@ -69,7 +69,7 @@ kubectl -n cattle-namespace logs -f rancher-784d94f59b-vgqzh
|
||||
|
||||
Use your browser to check the certificate details. If it says the Common Name is "Kubernetes Ingress Controller Fake Certificate", something may have gone wrong with reading or issuing your SSL cert.
|
||||
|
||||
> Note: if you are using LetsEncrypt to issue certs it can sometimes take a few minuets to issue the cert.
|
||||
> **NOTE:** if you are using LetsEncrypt to issue certs it can sometimes take a few minuets to issue the cert.
|
||||
|
||||
#### cert-manager issued certs (Rancher Generated or LetsEncrypt)
|
||||
|
||||
|
||||
+13
-1
@@ -30,7 +30,19 @@ const bootstrapDocsSearch = function() {
|
||||
autofocus: true,
|
||||
loadingIndicator: true,
|
||||
container: '#search-box',
|
||||
placeholder: 'Search Docs...',
|
||||
placeholder: 'Search Blog, Events, etc...',
|
||||
magnifier: false,
|
||||
reset: true,
|
||||
})
|
||||
);
|
||||
|
||||
|
||||
search.addWidget(
|
||||
instantsearch.widgets.searchBox({
|
||||
autofocus: true,
|
||||
loadingIndicator: true,
|
||||
container: '#search-box-mobile',
|
||||
placeholder: 'Search Blog, Events, etc...',
|
||||
magnifier: false,
|
||||
reset: true,
|
||||
})
|
||||
|
||||
Reference in New Issue
Block a user