[WIP] Add assertion to monitoring-plugin service

[danielmellado]

This PR adds some assertion and tests to ensure that the monitoring
plugin service exists and is reachable

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielmellado

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

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

[danielmellado]

/hold

[openshift-ci]

@danielmellado: 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
ci/prow/unit	ff771f9	link	true	/test unit
ci/prow/generate	ff771f9	link	true	/test generate
ci/prow/e2e-aws-ovn	ff771f9	link	true	/test e2e-aws-ovn
ci/prow/e2e-agnostic-operator	ff771f9	link	true	/test e2e-agnostic-operator
ci/prow/rules	ff771f9	link	true	/test rules
ci/prow/e2e-aws-ovn-single-node	ff771f9	link	false	/test e2e-aws-ovn-single-node
ci/prow/versions	ff771f9	link	false	/test versions
ci/prow/e2e-aws-ovn-upgrade	ff771f9	link	true	/test e2e-aws-ovn-upgrade
ci/prow/jsonnet-fmt	ff771f9	link	true	/test jsonnet-fmt
ci/prow/e2e-aws-ovn-techpreview	ff771f9	link	true	/test e2e-aws-ovn-techpreview
ci/prow/verify	ff771f9	link	true	/test verify
ci/prow/go-fmt	ff771f9	link	true	/test go-fmt
ci/prow/golangci-lint	ff771f9	link	true	/test golangci-lint
ci/prow/vendor	ff771f9	link	true	/test vendor
ci/prow/images	ff771f9	link	true	/test images

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.