mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-19 11:25:15 +00:00
Merge pull request #2220 from catherineluse/install-reorg
Minor updates for consistency
This commit is contained in:
Catherine Luse
GitHub
@@ -8,6 +8,6 @@ aliases:
|
||||
This section contains information about how to create backups of your Rancher data and how to restore them in a disaster scenario.
|
||||
|
||||
- [Docker Install Backups](./single-node-backups/)
|
||||
- [High Availability Install Backups](./ha-backups/)
|
||||
- [Kubernetes Install Backups](./ha-backups/)
|
||||
|
||||
If you are looking to back up your [Rancher launched Kubernetes cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/), please refer [here]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/backing-up-etcd/).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Creating Backups—High Availability Installs
|
||||
title: Creating Backups for Rancher Installed on Kubernetes
|
||||
weight: 50
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/after-installation/k8s-install-backup-and-restoration/
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Creating Backups—Docker Installs
|
||||
title: Creating Backups for Rancher Installed with Docker
|
||||
weight: 25
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/
|
||||
|
||||
@@ -5,6 +5,6 @@ weight: 1010
|
||||
If you lose the data on your Rancher Server, you can restore it if you have backups stored in a safe location.
|
||||
|
||||
- [Restoring Backups—Docker Installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/single-node-restoration/)
|
||||
- [Restoring Backups—High Availability Installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/ha-restoration/)
|
||||
- [Restoring Backups—Kubernetes installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/ha-restoration/)
|
||||
|
||||
If you are looking to restore your [Rancher launched Kubernetes cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/), please refer [here]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/restoring-etcd/).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Restoring Backups—High Availability Installs
|
||||
title: Restoring Backups—Kubernetes installs
|
||||
weight: 370
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/after-installation/ha-backup-and-restoration/
|
||||
|
||||
@@ -12,7 +12,7 @@ New password for default administrator (user-xxxxx):
|
||||
<new_password>
|
||||
```
|
||||
|
||||
High Availability install (Helm):
|
||||
Kubernetes install (Helm):
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
$ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- reset-password
|
||||
@@ -20,7 +20,7 @@ New password for default administrator (user-xxxxx):
|
||||
<new_password>
|
||||
```
|
||||
|
||||
High Availability install (RKE add-on):
|
||||
Kubernetes install (RKE add-on):
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
$ kubectl --kubeconfig $KUBECONFIG exec -n cattle-system $(kubectl --kubeconfig $KUBECONFIG get pods -n cattle-system -o json | jq -r '.items[] | select(.spec.containers[].name=="cattle-server") | .metadata.name') -- reset-password
|
||||
@@ -38,7 +38,7 @@ New password for default administrator (user-xxxxx):
|
||||
<new_password>
|
||||
```
|
||||
|
||||
High Availability install (Helm):
|
||||
Kubernetes install (Helm):
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
$ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin
|
||||
@@ -46,7 +46,7 @@ New password for default administrator (user-xxxxx):
|
||||
<new_password>
|
||||
```
|
||||
|
||||
High Availability install (RKE add-on):
|
||||
Kubernetes install (RKE add-on):
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
$ kubectl --kubeconfig $KUBECONFIG exec -n cattle-system $(kubectl --kubeconfig $KUBECONFIG get pods -n cattle-system -o json | jq -r '.items[] | select(.spec.containers[].name=="cattle-server") | .metadata.name') -- ensure-default-admin
|
||||
@@ -70,7 +70,7 @@ $ docker exec -ti <container_id> loglevel --set info
|
||||
OK
|
||||
```
|
||||
|
||||
* High Availability install (Helm)
|
||||
* Kubernetes install (Helm)
|
||||
* Enable
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
@@ -90,7 +90,7 @@ OK
|
||||
OK
|
||||
```
|
||||
|
||||
* High Availability install (RKE add-on)
|
||||
* Kubernetes install (RKE add-on)
|
||||
* Enable
|
||||
```
|
||||
$ KUBECONFIG=./kube_config_rancher-cluster.yml
|
||||
@@ -121,7 +121,7 @@ The Layer-4 Load Balancer is created as `type: LoadBalancer`. In Kubernetes, thi
|
||||
### Where is the state of Rancher stored?
|
||||
|
||||
- Docker Install: in the embedded etcd of the `rancher/rancher` container, located at `/var/lib/rancher`.
|
||||
- High Availability install: in the etcd of the RKE cluster created to run Rancher.
|
||||
- Kubernetes install: in the etcd of the RKE cluster created to run Rancher.
|
||||
|
||||
### How are the supported Docker versions determined?
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ Rancher is installed using the Helm package manager for Kubernetes. Helm charts
|
||||
|
||||
With Helm, we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at https://helm.sh/.
|
||||
|
||||
For systems without direct internet access, see [Air Gap: High Availability Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/).
|
||||
For systems without direct internet access, see [Air Gap: Kubernetes install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/).
|
||||
|
||||
To choose a Rancher version to install, refer to [Choosing a Rancher Version.]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags)
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ weight: 190
|
||||
|
||||
Use RKE to install a Kubernetes cluster on your three nodes using a high-availability etcd configuration.
|
||||
|
||||
For systems without direct internet access, refer to [Air Gap: High Availability Install.]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
For systems without direct internet access, refer to [Air Gap: Kubernetes install.]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
|
||||
> **Single-node Installation Tip:**
|
||||
> In a single-node Kubernetes cluster, the Rancher server does not have high availability, which is important for running Rancher in production. However, installing Rancher on a single-node cluster can be useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path.
|
||||
|
||||
@@ -147,7 +147,7 @@ kubectl -n cattle-system create secret generic tls-ca-additional --from-file=ca-
|
||||
For details on installing Rancher with a private registry, see:
|
||||
|
||||
- [Air Gap: Docker Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-single-node/)
|
||||
- [Air Gap: High Availability Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
- [Air Gap: Kubernetes Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
|
||||
### External TLS Termination
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ weight: 200
|
||||
|
||||
Rancher installation is managed using the Helm package manager for Kubernetes. Use `helm` to install the prerequisite and charts to install Rancher.
|
||||
|
||||
For systems without direct internet access, see [Air Gap: High Availability Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/).
|
||||
For systems without direct internet access, see [Air Gap: Kubernetes install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/).
|
||||
|
||||
Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
|
||||
|
||||
|
||||
+1
-1
@@ -143,7 +143,7 @@ kubectl -n cattle-system create secret generic tls-ca-additional --from-file=ca-
|
||||
For details on installing Rancher with a private registry, see:
|
||||
|
||||
- [Air Gap: Docker Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-single-node/)
|
||||
- [Air Gap: High Availability Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
- [Air Gap: Kubernetes Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
|
||||
|
||||
|
||||
### External TLS Termination
|
||||
|
||||
@@ -5,7 +5,7 @@ weight: 190
|
||||
|
||||
Use RKE to install Kubernetes with a high availability etcd configuration.
|
||||
|
||||
>**Note:** For systems without direct internet access see [Air Gap: High Availability Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/) for install details.
|
||||
>**Note:** For systems without direct internet access see [Air Gap: Kubernetes install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/) for install details.
|
||||
|
||||
### Create the `rancher-cluster.yml` File
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ weight: 276
|
||||
>If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
|
||||
|
||||
|
||||
* [High Availability Installation with External Load Balancer (TCP/Layer 4)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-4-lb)
|
||||
* [High Availability Installation with External Load Balancer (HTTPS/Layer 7)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-7-lb)
|
||||
* [HTTP Proxy Configuration for a High Availability Installation]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/proxy/)
|
||||
* [Kubernetes installation with External Load Balancer (TCP/Layer 4)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-4-lb)
|
||||
* [Kubernetes installation with External Load Balancer (HTTPS/Layer 7)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-7-lb)
|
||||
* [HTTP Proxy Configuration for a Kubernetes installation]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/proxy/)
|
||||
* [Troubleshooting RKE Add-on Installs]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/troubleshooting/)
|
||||
|
||||
@@ -21,9 +21,9 @@ NO_PROXY | Network address(es), network address range(s) and do
|
||||
|
||||
> **Note** NO_PROXY must be in uppercase to use network range (CIDR) notation.
|
||||
|
||||
## High Availability Installation
|
||||
## Kubernetes installation
|
||||
|
||||
When using High Availability Installation, the environment variables need to be added to the RKE Config File template.
|
||||
When using Kubernetes installation, the environment variables need to be added to the RKE Config File template.
|
||||
|
||||
* [Kubernetes Installation with External Load Balancer (TCP/Layer 4) RKE Config File Template]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install-server-install/#5-download-rke-config-file-template)
|
||||
* [Kubernetes Installation with External Load Balancer (HTTPS/Layer 7) RKE Config File Template]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install-server-install-external-lb/#5-download-rke-config-file-template)
|
||||
|
||||
+1
-1
@@ -11,7 +11,7 @@ aliases:
|
||||
>
|
||||
>If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
|
||||
|
||||
This section contains common errors seen when setting up a High Availability Installation.
|
||||
This section contains common errors seen when setting up a Kubernetes installation.
|
||||
|
||||
Choose from the following options:
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ In an air gapped installation of Rancher, you will need to configure Rancher to
|
||||
|
||||
In Rancher v2.3.0, a local copy of `system-charts` has been packaged into the `rancher/rancher` container. To be able to use these features in an air gap install, you will need to run the Rancher install command with an extra environment variable, `CATTLE_SYSTEM_CATALOG=bundled`, which tells Rancher to use the local copy of the charts instead of attempting to fetch them from GitHub.
|
||||
|
||||
Example commands for a Rancher installation with a bundled `system-charts` are included in the [air gap Docker installation]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-single-node/install-rancher) instructions and the [air gap high availability installation]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/install-rancher/#c-install-rancher) instructions.
|
||||
Example commands for a Rancher installation with a bundled `system-charts` are included in the [air gap Docker installation]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-single-node/install-rancher) instructions and the [air gap Kubernetes installation]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/install-rancher/#c-install-rancher) instructions.
|
||||
|
||||
# Setting Up System Charts for Rancher Prior to v2.3.0
|
||||
|
||||
|
||||
@@ -11,5 +11,5 @@ weight: 276
|
||||
|
||||
- [Kubernetes Installation with External Load Balancer (TCP/Layer 4)]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/layer-4-lb)
|
||||
- [Kubernetes Installation with External Load Balancer (HTTPS/Layer 7)]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/layer-7-lb)
|
||||
- [HTTP Proxy Configuration for a High Availability Installation]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/proxy/)
|
||||
- [HTTP Proxy Configuration for a Kubernetes installation]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/proxy/)
|
||||
- [Troubleshooting RKE Add-on Installs]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/troubleshooting/)
|
||||
|
||||
@@ -25,7 +25,7 @@ NO_PROXY | Network address(es), network address range(s) and do
|
||||
|
||||
## Installing Rancher on a Kubernetes Cluster
|
||||
|
||||
When using High Availability Installation, the environment variables need to be added to the RKE Config File template.
|
||||
When using Kubernetes installation, the environment variables need to be added to the RKE Config File template.
|
||||
|
||||
* [Kubernetes Installation with External Load Balancer (TCP/Layer 4) RKE Config File Template]({{<baseurl>}}/rancher/v2.x/en/installation/ha-server-install/#5-download-rke-config-file-template)
|
||||
* [Kubernetes Installation with External Load Balancer (HTTPS/Layer 7) RKE Config File Template]({{<baseurl>}}/rancher/v2.x/en/installation/ha-server-install-external-lb/#5-download-rke-config-file-template)
|
||||
|
||||
@@ -11,7 +11,7 @@ aliases:
|
||||
>
|
||||
>If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
|
||||
|
||||
This section contains common errors seen when setting up a High Availability Installation.
|
||||
This section contains common errors seen when setting up a Kubernetes installation.
|
||||
|
||||
Choose from the following options:
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ A Kubernetes installation is comprised of three nodes running the Rancher server
|
||||
|
||||
These instructions also cover how to install Rancher on a single node in an air gapped environment.
|
||||
|
||||
The single-node Docker installation is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server.
|
||||
The Docker installation is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server.
|
||||
|
||||
> **Important:** If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker Installation to a Kubernetes Installation.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Installation Requirements
|
||||
description: Learn the node requirements for each node running Rancher server when you’re configuring Rancher to run either in a single-node or high-availability setup
|
||||
description: Learn the node requirements for each node running Rancher server when you’re configuring Rancher to run either in a Docker or Kubernetes setup
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/references
|
||||
|
||||
+2
-2
@@ -67,8 +67,8 @@ The benefit of using xip.io is that you obtain a working entrypoint URL immediat
|
||||
|
||||
#### Tutorials
|
||||
|
||||
- [High Availability Installation with External Load Balancer (HTTPS/Layer 7)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb)
|
||||
- [High Availability Installation with External Load Balancer (TCP/Layer 4)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install)
|
||||
- [Kubernetes installation with External Load Balancer (HTTPS/Layer 7)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb)
|
||||
- [Kubernetes installation with External Load Balancer (TCP/Layer 4)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install)
|
||||
- [Docker Installation with External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install-external-lb)
|
||||
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ In Kubernetes Installations of Rancher, the Rancher server cluster should also b
|
||||
|
||||
# Why HA is Better for Rancher in Production
|
||||
|
||||
We recommend installing the Rancher server on a three-node Kubernetes cluster for production, primarily because it protects the data stored on etcd. The Rancher server stores its data in etcd in both single-node and Kubernetes Installations.
|
||||
We recommend installing the Rancher server on a three-node Kubernetes cluster for production, primarily because it protects the Rancher server data. The Rancher server stores its data in etcd in both single-node and Kubernetes Installations.
|
||||
|
||||
When Rancher is installed on a single node, if the node goes down, there is no copy of the etcd data available on other nodes and you could lose the data on your Rancher server.
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ The diagram below shows how users can manipulate both [Rancher-launched Kubernet
|
||||
|
||||
You can install Rancher on a single node, or on a high-availability Kubernetes cluster.
|
||||
|
||||
A high-availability installation is recommended for production. A Docker installation may be used for development and testing purposes, but there is no migration path from a single-node to a high-availability installation. Therefore, you may want to use a high-availability installation from the start.
|
||||
A high-availability Kubernetes installation is recommended for production. A Docker installation may be used for development and testing purposes, but there is no migration path from a single-node to a high-availability installation. Therefore, you may want to use a Kubernetes installation from the start.
|
||||
|
||||
The Rancher server, regardless of the installation method, should always run on nodes that are separate from the downstream user clusters that it manages. If Rancher is installed on a high-availability Kubernetes cluster, it should run on a separate cluster from the cluster(s) it manages.
|
||||
|
||||
|
||||
@@ -13,8 +13,8 @@ aliases:
|
||||
|
||||
In the event that your Rancher Server does not upgrade successfully, you can rollback to your installation prior to upgrade:
|
||||
|
||||
- [Single-Node Rollbacks]({{< baseurl >}}/rancher/v2.x/en/upgrades/single-node-rollbacks)
|
||||
- [High-Availability Rollbacks]({{< baseurl >}}/rancher/v2.x/en/upgrades/ha-server-rollbacks)
|
||||
- [Rollbacks for Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/single-node-rollbacks)
|
||||
- [Rollbacks for Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/ha-server-rollbacks)
|
||||
|
||||
> **Note:** If you are rolling back to versions in either of these scenarios, you must follow some extra [instructions]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks/) in order to get your clusters working.
|
||||
>
|
||||
|
||||
@@ -4,8 +4,8 @@ weight: 1010
|
||||
---
|
||||
This section contains information about how to rollback your Rancher server to a previous version.
|
||||
|
||||
- [Rolling back a Docker Install]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/)
|
||||
- [Rolling back a High Availability Install]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/)
|
||||
- [Rolling back Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/)
|
||||
- [Rolling back Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/)
|
||||
|
||||
### Special Scenarios regarding Rollbacks
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ aliases:
|
||||
|
||||
If you upgrade Rancher and the upgrade does not complete successfully, you may need to rollback your Rancher Server to its last healthy state.
|
||||
|
||||
To restore Rancher follow the procedure detailed here: [Restoring Backups — High Availability Installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/ha-restoration)
|
||||
To restore Rancher follow the procedure detailed here: [Restoring Backups — Kubernetes installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/ha-restoration)
|
||||
|
||||
Restoring a snapshot of the Rancher Server cluster will revert Rancher to the version and state at the time of the snapshot.
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Single Node Rollback
|
||||
title: Docker Rollback
|
||||
weight: 1015
|
||||
aliases:
|
||||
- /rancher/v2.x/en/backups/rollbacks/single-node-rollbacks
|
||||
- /rancher/v2.x/en/upgrades/single-node-rollbacks
|
||||
---
|
||||
|
||||
If a Rancher upgrade does not complete successfully, you'll have to roll back to your Rancher setup that you were using before [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade). Rolling back restores:
|
||||
If a Rancher upgrade does not complete successfully, you'll have to roll back to your Rancher setup that you were using before [Docker Upgrade]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade). Rolling back restores:
|
||||
|
||||
- Your previous version of Rancher.
|
||||
- Your data backup created before upgrade.
|
||||
|
||||
@@ -325,4 +325,4 @@ Remove the previous Rancher Server container. If you only stop the previous Ranc
|
||||
|
||||
## Rolling Back
|
||||
|
||||
If your upgrade does not complete successfully, you can roll back Rancher server and its data back to its last healthy state. For more information, see [Single Node Rollback]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/).
|
||||
If your upgrade does not complete successfully, you can roll back Rancher server and its data back to its last healthy state. For more information, see [Docker Rollback]({{< baseurl >}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/).
|
||||
|
||||
@@ -26,11 +26,11 @@ Before installing v2.x, provision one host or more to function as your Rancher S
|
||||
|
||||
After provisioning your node(s), install Rancher:
|
||||
|
||||
- [Docker Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node)
|
||||
- [Docker Install]({{<baseurl>}}/rancher/v2.x/en/installation/single-node)
|
||||
|
||||
For development environments, Rancher can be installed on a single node using Docker. This installation procedure deploys a single Rancher container to your host.
|
||||
|
||||
- [Kubernetes Install]({{< baseurl >}}/rancher/v2.x/en/installation/k8s-install/)
|
||||
- [Kubernetes Install]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/)
|
||||
|
||||
For production environments where your user base requires constant access to your cluster, we recommend installing Rancher in a high availability Kubernetes installation. This installation procedure provisions a three-node cluster and installs Rancher on each node using a Helm chart.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user