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

Make terminology consistent

Browse Source
This commit is contained in:
Catherine Luse
2020-01-27 16:59:02 -07:00
parent 9f80edfe8d
commit f8ae797a2b
5 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/_index.md
+1 -1
View File
@@ -52,7 +52,7 @@ helm fetch rancher-<CHART_REPO>/rancher
Rancher Server is designed to be secure by default and requires SSL/TLS configuration.
For HA air gap configurations, there are two recommended options for the source of the certificate.
When Rancher is installed on an air gapped Kubernetes cluster, there are two recommended options for the source of the certificate.
> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/helm-rancher/chart-options/#external-tls-termination).
content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
+2 -2
View File
@@ -59,9 +59,9 @@ If you have issues upgrading Rancher, roll it back to its latest known healthy s
```
You can obtain the name for your Rancher container by entering `docker ps`.
1. Move the backup tarball that you created during completion of [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/) onto your Rancher Server. Change to the directory that you moved it to. Enter `dir` to confirm that it's there.
1. Move the backup tarball that you created during completion of [Docker Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/) onto your Rancher Server. Change to the directory that you moved it to. Enter `dir` to confirm that it's there.
If you followed the naming convention we suggested in [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/), it will have a name similar to (`rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz`).
If you followed the naming convention we suggested in [Docker Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/), it will have a name similar to (`rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz`).
1. Run the following command to replace the data in the `rancher-data` container with the data in the backup tarball, replacing the [placeholder](#before-you-start). Don't forget to close the quotes.
content/rancher/v2.x/en/upgrades/upgrades/ha/_index.md
+2 -2
View File
@@ -79,7 +79,7 @@ of your Kubernetes cluster running Rancher server. You'll use the snapshot as a
This section describes how to upgrade normal (Internet-connected) or air gap installations of Rancher with Helm.
{{% tabs %}}
{{% tab "HA Upgrade" %}}
{{% tab "Kubernetes Upgrade" %}}
Get the values, which were passed with `--set`, from the current Rancher Helm chart that is installed.
@@ -133,7 +133,7 @@ Please refer the [Upgrading Cert-Manager]({{< baseurl >}}/rancher/v2.x/en/instal
{{% /tab %}}
{{% tab "HA Air Gap Upgrade" %}}
{{% tab "Kubernetes Air Gap Upgrade" %}}
1. Render the Rancher template using the same chosen options that were used when installing Rancher. Use the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools.
content/rancher/v2.x/en/upgrades/upgrades/ha/helm2/_index.md
+2 -2
View File
@@ -81,7 +81,7 @@ of your Kubernetes cluster running Rancher server. You'll use the snapshot as a
This section describes how to upgrade normal (Internet-connected) or air gap installations of Rancher with Helm.
{{% tabs %}}
{{% tab "HA Upgrade" %}}
{{% tab "Kubernetes Upgrade" %}}
Get the values, which were passed with `--set`, from the current Rancher Helm chart that is installed.
@@ -134,7 +134,7 @@ Please refer the [Upgrading Cert-Manager]({{< baseurl >}}/rancher/v2.x/en/instal
{{% /tab %}}
{{% tab "HA Air Gap Upgrade" %}}
{{% tab "Kubernetes Air Gap Upgrade" %}}
1. Render the Rancher template using the same chosen options that were used when installing Rancher. Use the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools.
content/rancher/v2.x/en/upgrades/upgrades/single-node/_index.md
+4 -4
View File
@@ -120,11 +120,11 @@ Get the options set from your current Rancher install
Choose from the following options:
* Single Node Upgrade
* Single Node Upgrade for Air Gap Installs
* Docker Upgrade
* Docker Upgrade for Air Gap Installs
{{% tabs %}}
{{% tab "Single Node Upgrade" %}}
{{% tab "Docker Upgrade" %}}
Select which option you had installed Rancher server
@@ -220,7 +220,7 @@ docker run -d --volumes-from rancher-data \
{{% /accordion %}}
{{% /tab %}}
{{% tab "Single Node Air Gap Upgrade" %}}
{{% tab "Docker Air Gap Upgrade" %}}
For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.