Getting EKS with Both Linux and Windows node running with Calico Networking

[nabbdl]

Getting EKS with Both Linux and Windows node running with Calico Networking

Expected Behavior

Getting EKS with Both Linux and Windows node running with Calico Networking
Getting Windows Pod IP addresses from Calico IPAM instead of AWS CNI

Current Behavior

Possible Solution

According to Tigera documentation "https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/requirements", it is required that "The VPC controllers must be installed to run Windows pods".
Does it means that it is impossible to use Calico Overlay on Windows Node ?

Steps to Reproduce (for bugs)

Deploying EKS using Terraform (with or without vpc-cni). Following Tigera documentation guidance
deployed first node group on Linux --> Calico Overlay works Perfectly.
deployed secondary node group on Windows --> Calico Overlay not Working.
I was able to start some pods on windows by enabling "enable-windows-ipam: true" but then no comminication was possible between linux and windows pods.

Context

Your Environment

• Calico version 3.29.1
• Calico dataplane (iptables, windows etc.)
• Kubernetes 1.31 (EKS)
• Operating System and version: WINDOWS_CORE_2022_x86_64
• Link to your project (optional):

[coutinhop]

@nabbdl can you post the output of kubectl get ippools -o yaml? This is just a hunch at this point, but Windows does not support VXLANCrosssubnet (or any IPIP) encapsulation, this could be the reason...