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
root@kwinlabmasaz0a01:~# kubectl logs -f tigera-operator-7c67d76845-rrvsj -n tigera-operator
{"level":"error","ts":"2024-03-28T20:18:35Z","logger":"controller_windows","msg":"Waiting for IPAMConfiguration watch to be established","reason":"ResourceNotReady","stacktrace":"github.com/tigera/operator/pkg/controller/status.(*statusManager).SetDegraded\n\t/go/src/github.com/tigera/operator/pkg/controller/status/status.go:356\ngithub.com/tigera/operator/pkg/controller/installation.(*ReconcileWindows).Reconcile\n\t/go/src/github.com/tigera/operator/pkg/controller/installation/windows_controller.go:328\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235"}
The text was updated successfully, but these errors were encountered:
We decide to migrate from calico manifest installation to Tigera Calico Operator on K8S cluster with Windows nodes.
Everything work (calico run fine) on Linux node
Nothing work on Windows node
No calico-node-win (pod/ds) are created.
Tigera Operator pod report this error message
"Waiting for IPAMConfiguration watch to be established"
Cluster before migration:
K8S 1.27.6
Calico 3.27.2 (installed with manifest)
Calico run fine on linux and windows node
Cluster after calico tigera operator migration:
K8S 1.27.6
Calico 3.27.2 ok on linux node
Nothing on windows node
The text was updated successfully, but these errors were encountered: