Update OpenTelemetry operator downstream CI to use opentelemetry-operator-system namespace

[IshwarKanse]

Summary

• Install the opentelemetry-product operator in the opentelemetry-operator-system namespace (previously openshift-opentelemetry-operator) across all downstream testing jobs (OCP 4.20, 4.21, 4.22)
• Update cluster-logging and loki-operator channels from stable-6.4 to stable-6.5 in the OCP 4.22 downstream job

Test plan

• Verify CI jobs trigger and install the OpenTelemetry operator in the correct namespace
• Verify logging/loki operators install from the stable-6.5 channel on OCP 4.22

🤖 Generated with Claude Code

Summary by CodeRabbit

Updated the OpenTelemetry operator downstream CI jobs for OCP 4.20, 4.21, and 4.22 to install opentelemetry-product into the opentelemetry-operator-system namespace instead of openshift-opentelemetry-operator.

For the OCP 4.22 downstream job, also bumped the cluster-logging and loki-operator channels from stable-6.4 to stable-6.5, keeping the rest of the operator install configuration unchanged.

[coderabbitai]

Walkthrough

Three downstream CI YAML configs for the OpenTelemetry operator are updated: the opentelemetry-product operator's install_namespace is changed from openshift-opentelemetry-operator to opentelemetry-operator-system across OCP 4.20, 4.21, and 4.22. The 4.22 config additionally bumps cluster-logging and loki-operator channels from stable-6.4 to stable-6.5.

Changes

OpenTelemetry Downstream CI Config Updates

Layer / File(s)	Summary
Namespace rename and channel bump across OCP 4.20–4.22 configs ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__opentelemetry-product-ocp-4.20-downstream.yaml, ...4.21-downstream.yaml, ...4.22-downstream.yaml	opentelemetry-product install_namespace is changed from openshift-opentelemetry-operator to opentelemetry-operator-system in all three OCP version configs. The 4.22 config also updates cluster-logging and loki-operator channel values from stable-6.4 to stable-6.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

lgtm, approved

Suggested reviewers

• danielmellado
• jgbernalp
• PeterYurkovich

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: switching downstream OpenTelemetry operator CI to the opentelemetry-operator-system namespace.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS: PR only updates CI YAML operator install namespaces/channels; no Ginkgo test titles (It/Describe/Context/When) were added or modified.
Test Structure And Quality	✅ Passed	PR only updates ci-operator YAML; no Ginkgo test files or It/Expect/Eventually code were changed, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only changes CI operator YAML namespaces/channels; no new Ginkgo tests or MicroShift-affected APIs/features were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only ci-operator YAML changed; no Ginkgo test files or It/Describe/Context/When additions were introduced, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PASS: The PR only edits ci-operator test config install namespaces/channels; no deployment manifests, replicas, affinity, nodeSelectors, spread constraints, or PDBs were added.
Ote Binary Stdout Contract	✅ Passed	PR only changes ci-operator YAML namespaces/channels; no process-level code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only ci-operator YAML changed; no new Ginkgo e2e test code or external connectivity logic was added, so this check is not implicated.
No-Weak-Crypto	✅ Passed	Touched YAML only changes operator namespaces/channels; no weak-crypto algorithms, custom crypto, or secret comparisons appear in the modified files.
Container-Privileges	✅ Passed	Changed CI YAMLs only adjust operator namespace/channel values; no privileged/root/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation settings were found.
No-Sensitive-Data-In-Logs	✅ Passed	Touched YAML only changes operator namespace/channels; no passwords, tokens, PII, or sensitive hostnames found.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@IshwarKanse: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-open-telemetry-opentelemetry-operator-main-opentelemetry-product-ocp-4.22-downstream-opentelemetry-downstream-tests	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-open-telemetry-opentelemetry-operator-main-opentelemetry-product-ocp-4.21-downstream-opentelemetry-downstream-tests	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-open-telemetry-opentelemetry-operator-main-opentelemetry-product-ocp-4.20-downstream-opentelemetry-downstream-tests	N/A	periodic	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[IshwarKanse]

/pj-rehearse

[openshift-merge-bot]

@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[IshwarKanse]

/pj-rehearse periodic-ci-openshift-open-telemetry-opentelemetry-operator-main-opentelemetry-product-ocp-4.21-downstream-opentelemetry-downstream-tests

[openshift-merge-bot]

@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[IshwarKanse]

/pj-rehearse ack

[openshift-merge-bot]

@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@IshwarKanse: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[pavolloffay]

LGTM,

do other jobs use the same namesapce?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IshwarKanse, pavolloffay

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/open-telemetry-opentelemetry-operator/OWNERS [IshwarKanse,pavolloffay]

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