This message was deleted.

Ok small update and progress: By using

curl -s -H "Authorization: Bearer xxxx" "<https://zzz/v3/clusterregistrationtokens?clusterId=c-xxx>" | jq -r '.data[] | .command'

I was able to see the yaml definition that should be deployed to the cluster what I did. When I deploy it to the broken cluster I notice that

cattle-cluster-agent

pds are created, but still on rancher side I see errors like:

[ERROR] failed to start cluster controllers c-xxxxx: context canceled

So I recheck the deployment from this import command with another cluster and notice about missing env like:

- name: CATTLE_FEATURES
  value: embedded-cluster-api=false,fleet=false,monitoringv1=false,multi-cluster-management=false,multi-cluster-management-agent=true,provisioningv2=false,rke2=false

So I add it also to my broken cluster and now the odd things. My cluster is no longer grayout on the list so I can click on it but still the label is Unavailable. on rancher logs I saw also

[ERROR] error syncing 'c-xxxxx': handler cluster-deploy: Unauthorized, requeuing

So it's odd for me as I can see the pods and resource metrics on rancher ui but somehow something missing Any clue what else or where can be misconfigured from rancher perspective?