https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
p
I'm wondering if this will mean I need to reprovision the local cluster and restore from backup
This is at least a cluster that I'm not super tied to for production (though this is also happening in my prod rancher) so I have tried modifying the label 
<http://provider.cattle.io|provider.cattle.io>
to 
eks
that seems to have worked, but looking to here to know if that's an approved method of resolving
n
This usually happens when Rancher keeps old metadata from earlier cluster registration or upgrade migrations. Check the 
<http://clusters.management.cattle.io|clusters.management.cattle.io>
object for the local cluster and see if it still has 
rkeConfig
or old RKE1 annotations. If it does, Rancher will continue treating it as RKE1 even though the cluster is EKS. In most cases, the safest fix is re-importing the local cluster properly after a backup instead of manually editing provider fields.
3 Views
Open in Slack
PreviousNext
Powered by