OSD-22337 route some customer alerts to null receiver

[tkong-redhat]

There are some customer defined alerts which are picked up by CAMO and routed to Red Hat pagerduty due to customer set some labels with Red Hat managed namespaces.

Adding some route rules to redirect those alerts to NULL receiver so that Red Hat SRE will not be paged.

Rule has been tested on a stg cluster.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tkong-redhat Once this PR has been reviewed and has the lgtm label, please assign mmazur 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

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.19%. Comparing base (cdb7cd9) to head (328c19f). Report is 95 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #342      +/-   ##
==========================================
+ Coverage   66.01%   66.19%   +0.18%     
==========================================
  Files           7        7              
  Lines         915      920       +5     
==========================================
+ Hits          604      609       +5     
  Misses        288      288              
  Partials       23       23              

Files with missing lines	Coverage Δ
controllers/secret_controller.go	91.37% <100.00%> (+0.07%)	:arrow_up:

:rocket: New features to boost your workflow:

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

[dustman9000]

/hold for discussion

[openshift-ci[bot]]

@tkong-redhat: 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/test	328c19f3f165b9fb37918ae25c61bd7fb066e238	link	true	/test test
ci/prow/validate	328c19f3f165b9fb37918ae25c61bd7fb066e238	link	true	/test validate
ci/prow/coverage	328c19f3f165b9fb37918ae25c61bd7fb066e238	link	true	/test coverage
ci/prow/lint	328c19f3f165b9fb37918ae25c61bd7fb066e238	link	true	/test lint

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

[openshift-merge-robot]

PR needs rebase.

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.

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

@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.