MON-4071: GA MetricsCollectionProfiles

[rexagod]

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one when it doesn't exists.

[openshift-ci]

Hello @rexagod! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.0" version, but no target version was set.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow)
• Test runs (Sippy)

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 openshift-eng/jira-lifecycle-plugin repository.

[rexagod]

/jira refresh

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow)
• Test runs (Sippy)

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 openshift-eng/jira-lifecycle-plugin repository.

[rexagod]

/test e2e-aws-serial-techpreview
/test verify

[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-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

_The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one if it doesn't exist.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one if it doesn't exist.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one if it doesn't exist.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one when it doesn't exists.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rexagod: This pull request references MON-4071 which is a valid jira issue.

In response to this:

Tests: openshift/origin#28889

Other relevant PRs:

• MON-2693: Scrape profiles cluster-monitoring-operator#1785
• MON-3487: base CP enablement on dedicated feature gate cluster-monitoring-operator#2153
• MON-3231: add metric for the configured profile cluster-monitoring-operator#2030

---

• Periodic runs (Prow: openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview)
• Test runs (Sippy)

---

The failures observed for test suite on all metal platforms stem from the absence of cluster-monitoring-config (CMO's configuration manifest). I'll send a patch to create one when it doesn't exists.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@rexagod: 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/verify	c1b653a	link	true	/test verify
ci/prow/e2e-aws-serial-techpreview	c1b653a	link	true	/test e2e-aws-serial-techpreview
ci/prow/lint	c1b653a	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.