Scale down the original Rancher server #1953
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I was migrating my Rancher instance to a new cluster running RKE2 (the original local cluster was running RKE1), if followed the steps as described in https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster I found out that after i made the change on my DNS server - all the clusters that were registrated to my original Rancher server - were stuck on updating in the new Rancher server. I figured out that the cattle-cluster-agents were still communicating with the old Rancher server, and had to be restarted, or fail their connection with it - in order to make them communicate with the new Rancher server. I assume that more Rancher users can experience this problem, and this add to the Rancher migration guide will make their migrating operation easier.
OdedNeuhaus
requested review from
btat,
LucasSaintarbor,
pmkovar and
sunilarjun
as code owners
OdedNeuhaus
changed the title
pmkovar
reviewed
Aug 21, 2025
...uides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
Outdated
Show resolved
Hide resolved
...uides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
Outdated
Show resolved
Hide resolved
…-recovery/migrate-rancher-to-new-cluster.md Co-authored-by: Petr Kovar <[email protected]>
…-recovery/migrate-rancher-to-new-cluster.md Co-authored-by: Petr Kovar <[email protected]>
|
Okay, thank you very much for the reply :) |
|
That should be it, thanks again. |
pmkovar
added
the
port/community-product
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was migrating my Rancher 2.10.1 instance to a new cluster running RKE2 (the original local cluster was running RKE1), I followed the steps as described in:
https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster
I found out that after I made the change on my DNS server - all the clusters that were connected to my original Rancher server - were stuck on updating in the new Rancher server.
I figured out that the cattle-cluster-agents were still communicating with the old Rancher server, and had to fail their connection with it (or had to be restarted) - in order to make them communicate with the new Rancher server.
After I scaled down the the original Rancher server, the clusters became in Running state in the new Rancher server.
This is a very important step that wasn't mentioned in the migration guide.
I assume that more Rancher users can experience this problem when migrating their Rancher environment between clusters, and I think this addition to the Rancher migration guide will make their migrating operation easier (and possible).