🐛 Skip publishing the RemediationRestricted event when there are no unhealthy target

[Levi080513]

What this PR does / why we need it:

When there are no unhealthy target, skip publishing the RemediationRestricted event to avoid misleading.

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 # #10585

/area machinehealthcheck

[k8s-ci-robot]

Hi @Levi080513. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[enxebre]

Thanks!
/ok-to-test
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 70a04b05e6a21a1d1751700eab334e4d33fc2410

[sbueringer]

/lgtm

/assign @enxebre

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a9bcc65450f66e50ee50fe92b710746bf5b2b62f

[enxebre]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

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 [enxebre]

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

[Levi080513]

Can this PR cherry pick to 1.6? The main version we are currently using is still 1.6.

[sbueringer]

Fine for me

[sbueringer]

/cherry-pick release-1.7

[sbueringer]

/cherry-pick release-1.6

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #10616

In response to this:

/cherry-pick release-1.7

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]

@sbueringer: new pull request created: #10617

In response to this:

/cherry-pick release-1.6

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.