not casing

2026-09-25 04:28:15 +00:00 · 2018-09-14 13:10:50 -07:00
parent d05ec9fe86
commit a4a1354e7e
6 changed files with 8 additions and 8 deletions
@@ -95,7 +95,7 @@ Use RKE with the new `rancher-cluster-restore.yml` configuration and restore the
 rke etcd snapshot-restore --name <snapshot>.db --config ./rancher-cluster-restore.yml
 ```

-> **NOTE:** RKE will create an `etcd` container with the restored database on the "target node". This container will not complete the `etcd` initialization and stay in a running state until the cluster brought up in the next step.
+> **Note:** RKE will create an `etcd` container with the restored database on the "target node". This container will not complete the `etcd` initialization and stay in a running state until the cluster brought up in the next step.

 ### 5. Bring Up the Cluster

@@ -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/)
@@ -73,11 +73,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)

@@ -12,4 +12,4 @@ To restore Rancher follow the procedure detailed here: [Restoring Backups — Hi

 Restoring a snapshot of the Rancher Server cluster will revert Rancher to the version and state at the time of the snapshot.

-> **NOTE:** Managed cluster are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.
+> **Note:** Managed cluster are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.