「Rancher Requirements」修訂間的差異
跳至導覽
跳至搜尋
| 行 2： | 行 2： | ||
high-availability RKE cluster |
high-availability RKE cluster |
||
* '''Three Linux nodes''', typically virtual machines, in an infrastructure provider such as Amazon’s EC2, Google Compute Engine, or vSphere. |
* '''Three Linux nodes''', typically virtual machines, in an infrastructure provider such as Amazon’s EC2, Google Compute Engine, or vSphere. |
||
| + | : These nodes must be in the same region/data center. You may place these servers in separate availability zones. |
||
* '''A load balancer''' to direct front-end traffic to the three nodes. |
* '''A load balancer''' to direct front-end traffic to the three 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. |
||
於 2021年1月27日 (三) 14:28 的修訂
RKE
high-availability RKE cluster
- Three Linux nodes, typically virtual machines, in an infrastructure provider such as Amazon’s EC2, Google Compute Engine, or vSphere.
- These nodes must be in the same region/data center. You may place these servers in separate availability zones.
- A load balancer to direct front-end traffic to the three 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.