This message was deleted.
# rke2a
adamant-kite-43734
09/20/2024, 8:23 AMThis message was deleted.
f
full-receptionist-93017
09/21/2024, 1:34 AMDo you mean you want to remove your cluster from rancher, and move it to another instance of rancher?
full-receptionist-93017
09/21/2024, 1:38 AMIf so, check out https://github.com/rancher/rancher-cleanup
full-receptionist-93017
09/21/2024, 1:39 AMI've used it in a test rancher environment to break the relationship between an rke2 cluster managed by rancher, and add it back again.
full-receptionist-93017
09/21/2024, 1:41 AMBe aware that projects are a rancher concept, so if you are using projects to hold namespaces, all of those namespaces will move to the "Not in a Project" project. The workloads will be fine, but you'll have to rebuild the projects.
full-receptionist-93017
09/21/2024, 1:42 AMOh, and RBAC will be affected if you are granting users access to projects.
p
powerful-librarian-10572
09/22/2024, 12:31 PMYeah exactly, after breaking that relationship, you just had to import it as a generic kubes cluster?
f
full-receptionist-93017
09/22/2024, 12:32 PMCorrect. In fact, this was a test cluster, and I deleted it and added it back to the same rancher server multiple times without issue.
full-receptionist-93017
09/22/2024, 12:33 PMThe cleanup will leave a completed job or two around that you can delete afterward, but they will only be an issue if you want to run the cleanup job again on the same rke cluster.
p
powerful-librarian-10572
09/23/2024, 7:52 AMMany thanks
m
melodic-night-19928
09/23/2024, 8:28 PMthat is very helpful information, thank you
3 Views