public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Replace 'Rancher Manager' with 'Rancher instance'

Browse Source
This commit is contained in:
Catherine Luse
2022-09-21 21:59:35 -07:00
parent 3af57431a0
commit a0268ab8b4
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference-guides/best-practices/rancher-server/rancher-deployment-strategy.md
+8 -8
View File
@@ -3,7 +3,7 @@ title: Rancher Deployment Strategy
weight: 100
---
There are two recommended deployment strategies for a Rancher Manager server that manages downstream Kubernetes clusters. Each one has its own pros and cons. Read more about which one would fit best for your use case:
There are two recommended deployment strategies for a Rancher instance that manages downstream Kubernetes clusters. Each one has its own pros and cons. Read more about which one would fit best for your use case:
* [Hub and Spoke](#hub-and-spoke-strategy)
* [Regional](#regional-strategy)
@@ -11,27 +11,27 @@ There are two recommended deployment strategies for a Rancher Manager server tha
## Hub & Spoke Strategy
---
In this deployment scenario, there is a single Rancher Manager instance managing Kubernetes clusters across the globe. The Rancher Manager would be run on a high-availability Kubernetes cluster, and there would be impact due to latencies.
In this deployment scenario, there is a single Rancher instance managing Kubernetes clusters across the globe. The Rancher instance would be run on a high-availability Kubernetes cluster, and there would be impact due to latencies.
### Pros
* Single control plane interface to view/see all regions and environments.
* Kubernetes does not require Rancher to operate and can tolerate losing connectivity to the Rancher Manager instance.
* Kubernetes does not require Rancher to operate and can tolerate losing connectivity to the Rancher instance.
### Cons
* Subject to network latencies.
* If the Rancher Manager instance goes down, global provisioning of new services is unavailable until it is restored. However, each Kubernetes cluster can continue to be managed individually.
* If Rancher goes down, global provisioning of new services is unavailable until it is restored. However, each Kubernetes cluster can continue to be managed individually.
## Regional Strategy
---
In the regional deployment model a Rancher Manager instance is deployed in close proximity to the downstream Kubernetes clusters.
In the regional deployment model a Rancher instance is deployed in close proximity to the downstream Kubernetes clusters.
### Pros
* Rancher functionality in regions stay operational if a Rancher Manager in another region goes down.
* Network latency between Rancher Manager and downstream clusters is greatly reduced, improving the performance of functionality in Rancher.
* Upgrades of Rancher Manager can be done independently per region.
* Rancher functionality in regions stay operational if a Rancher instance in another region goes down.
* Network latency between Rancher and downstream clusters is greatly reduced, improving the performance of functionality in Rancher.
* Upgrades of Rancher can be done independently per region.
### Cons