diff --git a/content/rancher/v2.x/en/installation/_index.md b/content/rancher/v2.x/en/installation/_index.md index 735dfa7f9bf..543da469547 100644 --- a/content/rancher/v2.x/en/installation/_index.md +++ b/content/rancher/v2.x/en/installation/_index.md @@ -14,11 +14,11 @@ Choose from the following installation options: In this scenario, you install Rancher on a single Linux host and access it using an external load balancer/proxy. -- [High Availablity Installation]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install/) +- [High Availability Installation]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install/) This install scenario creates a new Kubernetes cluster dedicated to running Rancher Server in a high-availabilty (HA) configuration. -- [High Availablity Installation with External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb) +- [High Availability Installation with External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb) This install scenario creates a new Kubernetes cluster dedicated to running Rancher Server in a high-availabilty (HA) configuration. A load balancer is placed in front of the HA configuration. @@ -26,6 +26,14 @@ Choose from the following installation options: We also have instructions for a more specialized use case where you install Rancher Server in an environment without an Internet connection. -- [Operation behind a corporate proxy]({{< baseurl >}}/rancher/v2.x/en/installation/behind-corporate-proxy/) +- [Backups and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/) - If your Rancher installation runs behind a corporate proxy, this page provides information on how to configure your proxy. + This page lists the ports you must open to operate Rancher. + +- [Port Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/references/) + + This page lists the ports you must open to operate Rancher. + +- [Rancher HTTP Proxy Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/proxy-configuration/) + + If your Rancher installation runs behind a proxy, this page provides information on how to configure Rancher for your proxy. diff --git a/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md b/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md index 121cc3aec4e..bc0211ab92d 100644 --- a/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md +++ b/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md @@ -1,10 +1,10 @@ --- title: Backups and Restoration -weight: 360 +weight: 345 aliases: - /rancher/v2.x/en/installation/after-installation/ --- This section contains information about how to create backups of your Rancher data and how to restore them in a disaster scenario. -- For single node backup instructions, see -- for high-availability backup instructions, see +- For single node backup instructions, see [Single Node Backup and Restoration]({{< baseurl >}/rancher/v2.x/en/}) +- for high-availability backup instructions, see [High Availability Backup and Restoration]() diff --git a/content/rancher/v2.x/en/installation/behind-corporate-proxy/_index.md b/content/rancher/v2.x/en/installation/proxy-configuration/_index.md similarity index 60% rename from content/rancher/v2.x/en/installation/behind-corporate-proxy/_index.md rename to content/rancher/v2.x/en/installation/proxy-configuration/_index.md index b17151fcb36..4656ad38022 100644 --- a/content/rancher/v2.x/en/installation/behind-corporate-proxy/_index.md +++ b/content/rancher/v2.x/en/installation/proxy-configuration/_index.md @@ -1,30 +1,30 @@ --- -title: Operating Rancher Behind an HTTP Proxy -weight: 275 +title: Rancher HTTP Proxy Configuration +weight: 360 --- If you operate Rancher behind a proxy and you need to reach the Internet to perform tasks (such as using Helm catalogs), you must provide Rancher information about your proxy. -## Setting the `http_proxy` Environment Variable ## +### Setting the `http_proxy` Environment Variable -### Ubuntu ### +#### Ubuntu 1. Check if `http_proxy` is still defined: - ```bash - echo $http_proxy - ``` + ``` +echo $http_proxy + ``` - If it is empty, set the variable and store it in your account's environment using the following command: + If it is empty, set the variable and store it in your account's environment using the following command: - ```bash - echo "export http_proxy=http://:@:/" >> .profile - ``` + ``` +echo "export http_proxy=http://:@:/" >> .profile + ``` 2. Logout and then log back in to activate your changes. -## Start Rancher Container with Proxy Information ## +### Start Rancher Container with Proxy Information Ensure that your `http_proxy` environment variable is visible inside of Rancher's Docker container: -```bash +``` sudo docker run -d --restart=unless-stopped --volumes-from rancher-data -p 80:80 -p 443:443 -e HTTP_PROXY=$http_proxy -e HTTPS_PROXY=$http_proxy -e http_proxy=$http_proxy -e https_proxy=$http_proxy -e NO_PROXY="localhost,127.0.0.1" -e no_proxy="localhost,127.0.0.1" rancher/rancher ``` diff --git a/content/rancher/v2.x/en/installation/references/_index.md b/content/rancher/v2.x/en/installation/references/_index.md index beeeed0f55a..95f4faa5eae 100644 --- a/content/rancher/v2.x/en/installation/references/_index.md +++ b/content/rancher/v2.x/en/installation/references/_index.md @@ -1,5 +1,6 @@ --- title: Port Requirements +weight: 355 aliases: - /rancher/v2.x/en/hosts/amazon/#required-ports-for-rancher-to-work/ --- diff --git a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md index 9dd0b701d56..5b5205fca2e 100644 --- a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md @@ -2,7 +2,7 @@ title: High Availability Upgrade weight: 1020 --- -To upgrade Rancher 2.x running in a high availablity configuration, run an upgrade command that points to your upgrade config file. +To upgrade Rancher 2.x running in a high Availability configuration, run an upgrade command that points to your upgrade config file. >**Prerequisites:** > diff --git a/layouts/shortcodes/requirements_ha.html b/layouts/shortcodes/requirements_ha.html index f9e7665f88a..56ffe487a23 100644 --- a/layouts/shortcodes/requirements_ha.html +++ b/layouts/shortcodes/requirements_ha.html @@ -1,5 +1,5 @@
-

High Availablity Requirements

+

High Availability Requirements

  • RKE Cluster