mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-28 22:18:52 +00:00
versioning
This commit is contained in:
+1
-1
@@ -15,7 +15,7 @@ The recommended infrastructure for the Rancher-only Kubernetes cluster differs d
|
|||||||
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
||||||
|
|
||||||
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
||||||
- **A load balancer** to direct traffic to the two nodes.
|
- **A load balancer** to direct traffic to the nodes.
|
||||||
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
||||||
|
|
||||||
### 1. Set up Linux Nodes
|
### 1. Set up Linux Nodes
|
||||||
|
|||||||
+1
-1
@@ -19,7 +19,7 @@ These nodes must be in the same region. You may place these servers in separate
|
|||||||
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
||||||
|
|
||||||
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
||||||
- **A load balancer** to direct traffic to the two nodes.
|
- **A load balancer** to direct traffic to the nodes.
|
||||||
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
||||||
|
|
||||||
### 1. Set up Linux Nodes
|
### 1. Set up Linux Nodes
|
||||||
|
|||||||
+1
-1
@@ -19,7 +19,7 @@ These nodes must be in the same region. You may place these servers in separate
|
|||||||
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
||||||
|
|
||||||
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
||||||
- **A load balancer** to direct traffic to the two nodes.
|
- **A load balancer** to direct traffic to the nodes.
|
||||||
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
||||||
|
|
||||||
### 1. Set up Linux Nodes
|
### 1. Set up Linux Nodes
|
||||||
|
|||||||
+1
-1
@@ -19,7 +19,7 @@ These nodes must be in the same region. You may place these servers in separate
|
|||||||
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
||||||
|
|
||||||
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
||||||
- **A load balancer** to direct traffic to the two nodes.
|
- **A load balancer** to direct traffic to the nodes.
|
||||||
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
||||||
|
|
||||||
### 1. Set up Linux Nodes
|
### 1. Set up Linux Nodes
|
||||||
|
|||||||
+1
-1
@@ -19,7 +19,7 @@ These nodes must be in the same region. You may place these servers in separate
|
|||||||
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
|
||||||
|
|
||||||
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
- **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
|
||||||
- **A load balancer** to direct traffic to the two nodes.
|
- **A load balancer** to direct traffic to the nodes.
|
||||||
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
- **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
|
||||||
|
|
||||||
### 1. Set up Linux Nodes
|
### 1. Set up Linux Nodes
|
||||||
|
|||||||
Reference in New Issue
Block a user