Add MachineHealthCheck for control plane to private cluster e2e template

[nojnhuh]

What type of PR is this?
/kind flake

What this PR does / why we need it:

The private cluster e2e test seems to be hitting #5687. This PR ports the fix to most of the templates in #5696 to the private cluster template.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

NONE

[nojnhuh]

/test pull-cluster-api-provider-azure-e2e-optional

[nojnhuh]

For better CI signal:

/cherry-pick release-1.20
/cherry-pick release-1.19

[k8s-infra-cherrypick-robot]

@nojnhuh: once the present PR merges, I will cherry-pick it on top of release-1.19, release-1.20 in new PRs and assign them to you.

In response to this:

For better CI signal:

/cherry-pick release-1.20
/cherry-pick release-1.19

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.06%. Comparing base (316370d) to head (aba6778).
⚠️ Report is 148 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5801   +/-   ##
=======================================
  Coverage   53.06%   53.06%           
=======================================
  Files         279      279           
  Lines       29677    29677           
=======================================
  Hits        15749    15749           
  Misses      13112    13112           
  Partials      816      816           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nojnhuh]

/test pull-cluster-api-provider-azure-e2e-optional

[nojnhuh]

/test pull-cluster-api-provider-azure-e2e-optional

[nojnhuh]

Testing kubernetes/test-infra#35109:

/test pull-cluster-api-provider-azure-load-test-custom-builds
/test pull-cluster-api-provider-azure-load-test-dra-custom-builds

[nojnhuh]

/test pull-cluster-api-provider-azure-load-test-dra-custom-builds

[nojnhuh]

/test pull-cluster-api-provider-azure-load-test-dra-custom-builds

[nojnhuh]

/test pull-cluster-api-provider-azure-e2e
/test pull-cluster-api-provider-azure-e2e-optional

[nojnhuh]

/cherry-pick release-1.21

[k8s-infra-cherrypick-robot]

@nojnhuh: once the present PR merges, I will cherry-pick it on top of release-1.21 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.21

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.

[k8s-ci-robot]

@nojnhuh: 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-cluster-api-provider-azure-e2e-optional	aba6778	link	false	/test pull-cluster-api-provider-azure-e2e-optional

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.

[mboersma]

/lgtm
/approve

Failure in -optional test doesn't appear related to this template change.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 613a2fd4f3778101f5b5e642ad1437ec42f2027a

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mboersma

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mboersma]

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

[mboersma]

/cherry-pick release-1.21

[k8s-infra-cherrypick-robot]

@mboersma: once the present PR merges, I will cherry-pick it on top of release-1.21 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.21

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.

[k8s-infra-cherrypick-robot]

@mboersma: new pull request created: #5915

In response to this:

/cherry-pick release-1.21

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.

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #5916

In response to this:

For better CI signal:

/cherry-pick release-1.20
/cherry-pick release-1.19

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.

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #5917

In response to this:

For better CI signal:

/cherry-pick release-1.20
/cherry-pick release-1.19

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.