Open amapi opened 5 months ago
@coutinhop knows about this one.
I think the solution is to create the Calico API server, following these instructions: https://docs.tigera.io/calico/latest/operations/install-apiserver#install-the-api-server
We may need a docs update for the migration docs here too
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