Use capzicicommunity register for calico node and add defender excluson for containerd tmpmount

[marosset]

This should fix the issues being see in https://testgrid.k8s.io/sig-release-master-informing#capz-windows-master&exclude-non-failed-tests= and https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-capz-master-windows/2090774807804121088

I think the actual issue is the calico node image not mounting in sufficient time due to defender scanning but we should use the czapzicommunity pull-through azure container registery for all images coming form quay.io anyways for reliability

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marosset

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [marosset]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[zylxjtu]

agree that we should unify the image registery to capzcommunity, but for the other change, the failures seems happening on linux node (control plane) instead of windows node? https://storage.googleapis.com/kubernetes-ci-logs/logs/ci-kubernetes-e2e-capz-master-windows/2090820362051784704/build-log.txt

[marosset]

agree that we should unify the image registery to capzcommunity, but for the other change, the failures seems happening on linux node (control plane) instead of windows node? https://storage.googleapis.com/kubernetes-ci-logs/logs/ci-kubernetes-e2e-capz-master-windows/2090820362051784704/build-log.txt

yes, doh

[kubernetes-prow]

@marosset: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-e2e-capz-windows-2025-extension	cb69bf3	link	false	/test pull-e2e-capz-windows-2025-extension

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.