OPRUN-3599: Add OLM resource to relatedObjects

[perdasilva]

Description

All resources listed in .status.relatedObjects of the ClusterOperator resource will get picked up by must-gather.
Previously, the openshift-cluster-olm-operator namespace (and included resources: deployments, services, etc.), and the cluster scoped OLM resource were not getting picked up by must-gather. Only the o-c and catd resources, which are dynamically added to the ClusterOperator at start-up.

This PR introduces two changes:

• Updates the ClusterOperator manifest to include the openshift-cluster-olm-operator namespace and OLM resources in its .status.relatedObjects. This ensures that, in the event of catastrophic failure, the namespace, its resources, and the OLM resource get picked up by must-gather
• Updates the final list of relatedObjects to include these two resources, as the update will wipe the existing values. Thus, ensuring that the same resources are present in the must-gather for failures after the CO gets updated.

[perdasilva]

/hold test PR

[perdasilva]

/unhold

[joelanford]

/lgtm
/approve

[openshift-ci-robot]

@perdasilva: This pull request references OPRUN-3599 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

Description

All resources listed in .status.relatedObjects of the ClusterOperator resource will get picked up by must-gather.
Previously, the openshift-cluster-olm-operator namespace (and included resources: deployments, services, etc.), and the cluster scoped OLM resource were not getting picked up by must-gather. Only the o-c and catd resources, which are dynamically added to the ClusterOperator at start-up.

This PR introduces two changes:

• Updates the ClusterOperator manifest to include the openshift-cluster-olm-operator namespace and OLM resources in its .status.relatedObjects. This ensures that, in the event of catastrophic failure, the namespace, its resources, and the OLM resource get picked up by must-gather
• Updates the final list of relatedObjects to include these two resources, as the update will wipe the existing values. Thus, ensuring that the same resources are present in the must-gather for failures after the CO gets updated.

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.

[joelanford]

/hold cancel
/lgtm

[everettraven]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, joelanford, perdasilva

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 [everettraven,joelanford,perdasilva]

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]

/retest-required

Remaining retests: 0 against base HEAD 7120e60 and 2 for PR HEAD 45025e4 in total

[perdasilva]

/retest

[openshift-ci]

@perdasilva: all tests passed!

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

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-olm-operator
This PR has been included in build ose-cluster-olm-operator-container-v4.18.0-202411081440.p0.g1df7873.assembly.stream.el9.
All builds following this will include this PR.