limited-potato-16824
12/07/2022, 2:31 PMfleet-local
to fleet-defaul
by following the instructions here:
https://fleet.rancher.io/troubleshooting#migrate-the-local-cluster-to-the-fleet-default-cluster
After we initialized the move, I could see this in the logs:
rancher-5677f59677-shbs7 rancher 2022/12/07 12:39:42 [ERROR] error syncing 'local': handler provisioning-cluster-create: failed to create fleet-default/local <http://provisioning.cattle.io/v1|provisioning.cattle.io/v1>, Kind=
Cluster for provisioning-cluster-create local: admission webhook "<http://rancherauth.cattle.io|rancherauth.cattle.io>" denied the request: cluster name must be 63 characters or fewer, cannot be "local" nor of the form "c
-xxxxx", requeuing
While this was happening, the local clulster had been removed from the fleet-local
workspace but for the reason above it did not show up in fleet-default
. We managed to get the cluster back to fleet-local
again after editing the object, but it would have been nice to have all the "Continuous delivery" clusters in the same workspace. If you have any hints how to make that migration successful, please share 🙂