This message was deleted.
# general
a
This message was deleted.
r
Hi @bright-smartphone-36388
Would you be able to look at one of the kubeconfig secrets for a cluster and see what labels it has?
b
I am looking in local cluster, namespace: fleet-default (where the clusters are deployed) at the secret named: cluster_name-kubeconfig, it has no labels
r
No labels at all?
b
none
k get secret -n fleet-default cluster_name-kubeconfig -o yaml, no metadata.labels key
r
And can you confirm the version of
capi-controller-manager?
Is it 1.5.5 from the issue?
b
yes!
r
Ok, thanks for confirming that.
i
looks like someone faced a similar problem and rolled back: https://rancher-users.slack.com/archives/C01PHNP149L/p1711451619579799
r
I think I can see what the issue is. I can see how rolling back would fix the issue.
b
I confirm it also fixes the issues on my side, the downgrade solution from the ticket
r
Thats good, thanks @bright-smartphone-36388.
b
@rapid-van-91305 no problem! Since we are here I wanted to ask you if there is any procedure/steps to join the maintainer team. I am working on both rancher/harvester with production-ready clusters (some of which even had to have custom forks). I would love to help with these products.