adj: Remove instructions for deploying Rancher server#965
Conversation
Removing "please install Rancher on a separate server" as it is confusing for customers Signed-off-by: Brian Almeida <brian.almeida@suse.com>
github-actions
Bot
requested review from
akashraj4261,
dariavladykina and
jillian-maroket
|
Made changes to promote using three nodes instead of a single node. Signed-off-by: Brian Almeida <brian.almeida@suse.com>
jillian-maroket
requested review from
Vicente-Cheng
and removed request for
akashraj4261 and
dariavladykina
Vicente-Cheng
left a comment
Vicente-Cheng
left a comment
There was a problem hiding this comment.
Hmm, maybe we need to rephrase this section?
Indeed, we suggest installing the Rancher on the external (the vcluster is a special case).
If we remove this section, users might think, yes, we can install the external Rancher within the Harvester cluster.
But this is not the best practice we recommend.
cc @harvester/tpm, @ibrokethecloud, @ihcsim
|
@Vicente-Cheng I'm under the same impression that external Rancher is the recommended best practice. Either we leave the doc unchanged, and/or mention that vcluster is available as an experimental option, or simply combine line 34 and line 36 and let user decide what works best for them: "To use Rancher with Harvester, please follow the Deploying Rancher Server document to deploy and provision Rancher and a Kubernetes cluster with the provider of your choice." |
|
I would shy away from mentioning vcluster as the background leading up to this PR stems from a customer trying to leverage this feature and it not working as efficient as they were expecting. (In my testing, this is more on upstream vcluster then it is on Harvester) |
|
@jillian-maroket would you be able to review this PR, please? |
| To use Rancher with Harvester, you can create a HA setup with three VMs in Harvester and install the Rancher server by following the [Helm CLI quick start](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/helm-cli). | ||
|
|
||
| For production setup, please follow [Deploying Rancher Server document](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager) to deploy and provision Rancher and a Kubernetes cluster with the provider of your choice. |
There was a problem hiding this comment.
| To use Rancher with Harvester, you can create a HA setup with three VMs in Harvester and install the Rancher server by following the [Helm CLI quick start](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/helm-cli). | |
| For production setup, please follow [Deploying Rancher Server document](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager) to deploy and provision Rancher and a Kubernetes cluster with the provider of your choice. | |
| For production setups, you must install the Rancher server on a dedicated, high-availability Kubernetes cluster (with three or more nodes) deployed on infrastructure external to the Harvester cluster. Ensure that the cluster nodes meet the [software, hardware, and networking requirements](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements) outlined in the Rancher documentation. For more information, see [Deploying Rancher Server](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager). | |
| If you want to test the integration features, you can create a virtual machine in Harvester and then install the Rancher server using Helm. For more information, see the [Helm CLI Quick Start](https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/helm-cli). |
There was a problem hiding this comment.
I discussed this subject with a few engineers. This draft contains the information I got from them.
5 participants
Removing "please install Rancher on a separate server" as it is confusing for users
Problem:
Currently, the Intergrating with Rancher section in the documentation is contradicting itself and leaving readers confused.
Solution:
Remove the first sentence and combine with the following one to ensure readers are not confused when trying to intergrate Rancher with Harvester.
Related Issue(s):
Related issue: harvester/harvester#9969
Test plan:
Additional documentation or context