calicoNodeWindowsDaemonSet resources are ignored

[lghinet]

Hello,
setting calicoNodeWindowsDaemonSet resources in Installation CR does nothing

calico version - 3.31.3
tigera-operator - 1.40.3

thanks

[lghinet]

also if i want to use the deprecated componentResources the componentName: FelixWindows is not available, even if it should be

[tmjd]

I agree it looks like there are issues with both of those configuration methods.

calicoNodeWindowsDaemonSet

The container names look like they should be felix or node. But the validation is only allowing calico-node-windows

ComponentResource

I see kubebuilder:validation that would block being able to set the ComponentResource ComponentName to one of the windows ones. When you attempted to use the ComponentResource with a windows ComponentName, did doing kubectl apply reject the update?