Karmada created by karmada-operator doesn't have ConfigMap cluster-info in kube-public

[zyuce]

What happened:
I deployed a karmada cluster by karmada-operator, then I tried to create a member cluster with pull mode by using karmadactl register. I met the error as follow:

I0116 16:32:20.951683 580413 round_trippers.go:553] GET https://10.38.201.208:32563/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s 403 Forbidden in 21 milliseconds

I0116 16:32:20.952021 580413 request.go:1351] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"configmaps \"cluster-info\" is forbidden: User \"system:anonymous\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"kube-public\"","reason":"Forbidden","details":{"name":"cluster-info","kind":"configmaps"},"code":403}

I0116 16:32:20.952133 580413 register.go:1298] [discovery] Failed to request cluster-info, will try again: configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kube-public"

What you expected to happen:
Karmada-operator should create cluster-info when initing cluster, just like the karmadactl init: code link
I think this is a lack of some functions in the karmada-operator.

How to reproduce it (as minimally and precisely as possible):
1.Deploy a karmada-operator by helm link
2.Apply a operator.karmada.io/v1alpha1/karmada and wait for the cluster to be running.
3.Try to create a member cluster with pull mode by using "karmadactl token create" and "karmadactl register -v=10" link
4.Then you could find the error message above.

Anything else we need to know?:

Environment:

• Karmada version: v1.12.2
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version): v1.12.2

[zhzhuang-zju]

@zyuce You are correct. Karmada managed through karmada-operator cannot directly use the karmadactl register command due to the absence of some necessary resources, not just cluster-info. This issue is tracked in task #5916.