You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E1106 19:15:40.649295 60506 planner.go:93] "failed to executed the workflow" err="failed to apply aggregated APIService resource to karmada controlplane, err: namespaces \"test1\" not found" workflow=init karmada="test1/karmada-demo"
E1106 19:15:40.664007 60506 controller.go:324] "Reconciler error" err="[failed to apply aggregated APIService resource to karmada controlplane, err: namespaces \"test1\" not found, Operation cannot be fulfilled on karmadas.operator.karmada.io \"karmada-demo\": the object has been modified; please apply your changes to the latest version and try again]" controller="karmada" controllerGroup="operator.karmada.io" controllerKind="Karmada" Karmada="test1/karmada-demo" namespace="test1" name="karmada-demo" reconcileID=c3e5137b-2ae7-4291-82c9-13f941e5d2f6
The service needs to be created in the cluster's built-in ns karmada-system corresponding to the karmada control plane. However, the ns test1 where the CR is located is used in the code, so the error ns does not exist.
What you expected to happen:
karmada instance can be installed normally
How to reproduce it (as minimally and precisely as possible):
What happened:
When I installed the karmada instance through karmada-operator by referring to the documentation https://github.com/karmada-io/karmada/tree/master/operator#create-a-karmada-instance
I found an error.
The service needs to be created in the cluster's built-in ns karmada-system corresponding to the karmada control plane. However, the ns test1 where the CR is located is used in the code, so the error ns does not exist.
What you expected to happen:
karmada instance can be installed normally
How to reproduce it (as minimally and precisely as possible):
follow the doc https://github.com/karmada-io/karmada/tree/master/operator#create-a-karmada-instance
Anything else we need to know?:
It should be a bug introduced by this issue #3750
Environment:
kubectl-karmada version
orkarmadactl version
):The text was updated successfully, but these errors were encountered: