mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-24 20:18:18 +00:00
refactor links to long format
This commit is contained in:
Jason Greathouse
@@ -6,16 +6,16 @@ This section contains instructions for installing Rancher in development and pro
|
||||
|
||||
### Installation Options
|
||||
|
||||
- [Single Node Installation](single-node/)
|
||||
- [Single Node Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/)
|
||||
|
||||
Install Rancher on a single Linux host.
|
||||
|
||||
- [High Availability Installation](ha/)
|
||||
- [High Availability Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/ha/)
|
||||
|
||||
This install scenario creates a new Kubernetes cluster dedicated to running Rancher Server in a high-availability (HA) configuration.
|
||||
|
||||
### Reference
|
||||
|
||||
- [Port Requirements](references/)
|
||||
- [Port Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/references/)
|
||||
|
||||
List of required ports you must open to operate Rancher.
|
||||
|
||||
@@ -29,12 +29,12 @@ The following CLI tools are required for this install. Please make sure these to
|
||||
|
||||
## Installation Outline
|
||||
|
||||
1. [Create Nodes and Load Balancer](create-nodes-lb/)
|
||||
1. [Install Kubernetes with RKE](kubernetes-rke/)
|
||||
1. [Initialize Helm (tiller)](helm-init/)
|
||||
1. [Install Rancher](helm-rancher/)
|
||||
1. [Create Nodes and Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/ha/create-nodes-lb/)
|
||||
1. [Install Kubernetes with RKE]({{< baseurl >}}/rancher/v2.x/en/installation/ha/kubernetes-rke/)
|
||||
1. [Initialize Helm (tiller)]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/)
|
||||
1. [Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/)
|
||||
|
||||
## Additional Install Options
|
||||
|
||||
* [Migrating from RKE all-in-one install](migrating-from-rke-all-in-one/)
|
||||
* [RKE all-in-one install](rke-all-in-one/)
|
||||
* [Migrating from RKE all-in-one install]({{< baseurl >}}/rancher/v2.x/en/installation/ha/migrating-from-rke-all-in-one/)
|
||||
* [RKE all-in-one install]({{< baseurl >}}/rancher/v2.x/en/installation/ha/rke-all-in-one/)
|
||||
@@ -41,8 +41,8 @@ Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configurat
|
||||
|
||||
#### Examples
|
||||
|
||||
* [Amazon NLB](nlb/)
|
||||
* [Amazon NLB]({{< baseurl >}}/rancher/v2.x/en/installation/ha/create-nodes-lb/nlb/)
|
||||
|
||||
<br/>
|
||||
|
||||
### [Next: Install Kubernetes with RKE](../kubernetes-rke/)
|
||||
### [Next: Install Kubernetes with RKE]({{< baseurl >}}/rancher/v2.x/en/installation/ha/kubernetes-rke/)
|
||||
@@ -65,4 +65,4 @@ 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.
|
||||
|
||||
### [Next: Install Rancher](../helm-rancher/)
|
||||
### [Next: Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha//helm-rancher/)
|
||||
@@ -79,17 +79,17 @@ helm install rancher-stable/rancher --name rancher --namespace cattle-system \
|
||||
--set ingress.tls.source=secret
|
||||
```
|
||||
|
||||
Now that Rancher is running, see [Adding TLS Secrets](tls-secrets/) to publish the certificate files so Rancher and the Ingress Controller can use them.
|
||||
Now that Rancher is running, see [Adding TLS Secrets]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/) to publish the certificate files so Rancher and the Ingress Controller can use them.
|
||||
|
||||
### Advanced Configurations
|
||||
|
||||
The Rancher chart configuration has many options for customizing the install to suit your specific environment. Here are some common advanced scenarios.
|
||||
|
||||
* [HTTP Proxy](chart-options/#http-proxy)
|
||||
* [Private Docker Image Registry/Air Gap Network](chart-options/#private-or-air-gap-registry)
|
||||
* [TLS Termination on an External Load Balancer](chart-options/#external-tls-termination)
|
||||
* [HTTP Proxy]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/#http-proxy)
|
||||
* [Private Docker Image Registry/Air Gap Network]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/#private-or-air-gap-registry)
|
||||
* [TLS Termination on an External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/#external-tls-termination)
|
||||
|
||||
See the [Chart Options](chart-options/) for the full list of options.
|
||||
See the [Chart Options]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/) for the full list of options.
|
||||
|
||||
### Save your options
|
||||
|
||||
@@ -99,4 +99,4 @@ Make sure you save the `--set` options you used. You will need to use the same o
|
||||
|
||||
That's it you should have a functional Rancher server. Point a browser at the hostname you picked and you should be greeted by the colorful login page.
|
||||
|
||||
Doesn't Work? Take a look at the [Troubleshooting](troubleshooting/) Page
|
||||
Doesn't Work? Take a look at the [Troubleshooting]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/troubleshooting/) Page
|
||||
|
||||
@@ -76,7 +76,7 @@ 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](../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.
|
||||
|
||||
|
||||
@@ -76,6 +76,6 @@ Save a copy of the `kube_config_rancher-cluster.yml` and `rancher-cluster.yml` f
|
||||
|
||||
### Issues or errors?
|
||||
|
||||
See the [Troubleshooting](troubleshooting/) page.
|
||||
See the [Troubleshooting]({{< baseurl >}}/rancher/v2.x/en/installation/ha/kubernetes-rke/troubleshooting/) page.
|
||||
|
||||
### [Next: Initialize Helm](../helm-init/)
|
||||
### [Next: Initialize Helm]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/)
|
||||
@@ -31,7 +31,7 @@ SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10
|
||||
|
||||
##### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
|
||||
|
||||
* The key file specified as `ssh_key_path` is not correct for accesing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with.
|
||||
* The key file specified as `ssh_key_path` is not correct for accessing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with.
|
||||
|
||||
##### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys
|
||||
|
||||
|
||||
@@ -52,5 +52,5 @@ kubectl -n cattle-system delete serviceaccount cattle-admin
|
||||
|
||||
From here follow the standard install steps.
|
||||
|
||||
* [3 - Initialize Helm (Install tiller)](../helm-init/)
|
||||
* [4 - Install Rancher](../helm-rancher/)
|
||||
* [3 - Initialize Helm (Install tiller)]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/)
|
||||
* [4 - Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/)
|
||||
|
||||
@@ -5,6 +5,6 @@ weight: 276
|
||||
|
||||
Rancher can be installed by providing the appropriate Kubernetes manifest configurations to RKE's `addons` feature. See the following instructions for examples appropriate to your environment.
|
||||
|
||||
* [High Availability Installation with External Load Balancer (TCP/Layer 4)](layer-4-lb/)
|
||||
* [High Availability Installation with External Load Balancer (HTTPS/Layer 7)](layer-7-lb/)
|
||||
* [Troubleshooting RKE All-In-One Installs](troubleshooting/)
|
||||
* [High Availability Installation with External Load Balancer (TCP/Layer 4)]({{< baseurl >}}/rancher/v2.x/installation/ha/rke-all-in-one/layer-4-lb/)
|
||||
* [High Availability Installation with External Load Balancer (HTTPS/Layer 7)]({{< baseurl >}}/rancher/v2.x/installation/ha/rke-all-in-one/layer-7-lb/)
|
||||
* [Troubleshooting RKE All-In-One Installs]({{< baseurl >}}/rancher/v2.x/installation/ha/rke-all-in-one/troubleshooting/)
|
||||
|
||||
@@ -5,7 +5,7 @@ weight: 250
|
||||
For development environments, we recommend installing Rancher by running a single Docker container. In this installation scenario, you'll install Docker on a single Linux host, and then install Rancher on your host using a single Docker container.
|
||||
|
||||
>**Want to use an external load balancer?**
|
||||
> See [Single Node Installation with an External Load Balancer](advanced-options/single-node-install-external-lb) instead.
|
||||
> See [Single Node Installation with an External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/advanced-options/single-node-install-external-lb) instead.
|
||||
|
||||
## Installation Outline
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Advanced Install Options
|
||||
weight: 250
|
||||
---
|
||||
|
||||
* [Air Gap Installation](air-gap-installation)
|
||||
* [HTTP/S Proxy Configuration](proxy-configuration)
|
||||
* [Using an External Load Balancer](single-node-install-external-lb)
|
||||
* [Using a Private CA Root Certificate](private-ca-root-certificate)
|
||||
* [Air Gap Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/advanced-options/air-gap-installation)
|
||||
* [HTTP/S Proxy Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/advanced-options/proxy-configuration)
|
||||
* [Using an External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/advanced-options/single-node-install-external-lb)
|
||||
* [Using a Private CA Root Certificate]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/advanced-options/private-ca-root-certificate)
|
||||
+1
-1
@@ -8,7 +8,7 @@ For development environments, we recommend installing Rancher by running a singl
|
||||
|
||||
|
||||
>**Want to skip the external load balancer?**
|
||||
> See [Single Node Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install) instead.
|
||||
> See [Single Node Installation]({{< baseurl >}}/rancher/v2.x/en/installation/single-node) instead.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user