[release-1.27] Make a windows cloud-node-manager image based off the host-process-containers base image

[k8s-infra-cherrypick-robot]

This is an automated cherry-pick of #6318

/assign nojnhuh

Add a windows cloud-node-manager image based off of the host-process-containers base image

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: k8s-infra-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign nilo19 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[nojnhuh]

/assign @nilo19

[nojnhuh]

/retest

[k8s-ci-robot]

@k8s-infra-cherrypick-robot: The following tests 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-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz-1-27	8e171cd	link	true	/test pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz-1-27
pull-cloud-provider-azure-e2e-ccm-capz-1-27	8e171cd	link	true	/test pull-cloud-provider-azure-e2e-ccm-capz-1-27
pull-cloud-provider-azure-e2e-ccm-vmss-capz-1-27	8e171cd	link	true	/test pull-cloud-provider-azure-e2e-ccm-vmss-capz-1-27

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.

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.

[nilo19]

@nojnhuh 1.27 and 1.28 failed due to
s: "parameter 'activeDirectoryEndpoint' cannot be empty",

[nojnhuh]

@nilo19 Do you know why 1.29 and 1.30 don't fail with the same error?

[nilo19]

@nilo19 Do you know why 1.29 and 1.30 don't fail with the same error?

I thought this would be a capz problem, but now I don't think so. Let me do more research on cloud provider. Thanks!

[nojnhuh]

Could it be because #6622 has only been backported to 1.29 and 1.30?

[nilo19]

Could it be because #6622 has only been backported to 1.29 and 1.30?

It's here https://github.com/kubernetes-sigs/cloud-provider-azure/pull/6693/files