Can I move from self-managed Rancher to Rancher Prime Hosted?

This document (000020040) is provided subject to the disclaimer at the end of this document.

Resolution

Yes, we can do a one time migration of your entire self-hosted Rancher Manager into the Rancher Prime Hosted service. Requirements for migration are:

You must be running the latest stable version of Rancher (currently v2.8.1) for at least one week.
Rancher cluster must be running Kubernetes v1.25 or higher for at least one week.
All managed/downstream clusters must be running Kubernetes v1.25 or higher for at least one week.
Have a kubeconfig file for all your managed (downstream) Kubernetes clusters. The kubeconfig file should point directly to the cluster’s kube-apiserver endpoint and not to Rancher. For RKE clusters, see Authorized Cluster Endpoint for setup.
Authentication integration must be with a public endpoint that Rancher Prime Hosted can reach.
Global and cluster catalogs must have a public endpoint that Rancher Prime Hosted can reach.
Clusters provisioned using the vSphere node driver cannot be managed unless the vSphere API endpoint is made available to Rancher Prime Hosted.
All downstream/managed clusters must have outbound Internet access over port 443, or at least outbound access to Rancher Prime Hosted.
You must provide the output of Helm Chart values used to install Rancher: helm get values -n cattle-system rancher > rancher-values.yaml
You must provide a copy of the system summary report for your Rancher environment. See this article for instructions.

To get started on migrating to Rancher Prime Hosted, open a support case on our support portal.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.