OTEL operator remove P/Z jobs

[pavolloffay]

Summary by CodeRabbit

Removed OpenShift CI stage jobs for the OpenTelemetry Operator on:

• OpenShift 4.16 IBM Z
• OpenShift 4.17 IBM Power

This prevents these platform-specific stage jobs from being generated or executed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 7c2a3e69-19f9-4530-a7a0-3dea77b59936

📥 Commits

Reviewing files that changed from the base of the PR and between 2b7cd0a and 19910b3.

⛔ Files ignored due to path filters (2)

• ci-operator/jobs/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (2)

• ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__opentelemetry-product-ocp-4.16-ibm-z-stage.yaml
• ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__opentelemetry-product-ocp-4.17-ibm-p-stage.yaml

💤 Files with no reviewable changes (2)

• ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__opentelemetry-product-ocp-4.17-ibm-p-stage.yaml
• ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__opentelemetry-product-ocp-4.16-ibm-z-stage.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The change deletes two OpenShift CI configuration files for OpenTelemetry Operator IBM Z and IBM Power stage jobs on OpenShift 4.16 and 4.17.

Changes

Cohort / File(s)	Summary
IBM Z stage configuration removal ci-operator/config/openshift/open-telemetry-opentelemetry-operator/*ibm-*-stage.yaml	Deletes stage job definitions, including build settings, release metadata, test workflows, operator installation steps, resource settings, environment variables, and generated metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 19910

This change removes the specified P/Z test jobs and configurations; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the deletion of the OpenTelemetry Operator IBM Z and IBM Power jobs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.
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	The revision only deletes four CI YAML files (0 additions); the diff contains no Ginkgo It, Describe, Context, or When test-title changes.
Test Structure And Quality	✅ Passed	The diff changes only four YAML CI configuration/job files and contains no Ginkgo test code, assertions, waits, or resource setup; this check does not apply.
Microshift Test Compatibility	✅ Passed	The PR only deletes CI configuration and generated job entries. It adds no Ginkgo tests or test behavior, so no MicroShift-incompatible test was introduced.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit contains only deletions and no added or modified Go test files or Ginkgo declarations, so the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	The pull request only deletes CI configuration and generated job YAML; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only four CI YAML files and adds zero lines; it introduces no process-level code or stdout writes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request only deletes CI YAML and generated job entries; it adds no Ginkgo e2e tests or new IPv4 or external-connectivity behavior.
No-Weak-Crypto	✅ Passed	The PR only deletes CI configuration and job entries: all four changed files have 0 additions, and the complete patch contains no MD5, SHA1, DES, RC4, 3DES, Blowfish, or ECB terms.
Container-Privileges	✅ Passed	The commit contains only deletions: all four changed files add 0 lines, and no added line contains a forbidden privilege setting.
No-Sensitive-Data-In-Logs	✅ Passed	The commit contains only deletions, with no added logging or sensitive-data output; it cannot introduce exposure of passwords, tokens, PII, hostnames, or customer data.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [pavolloffay]
• ci-operator/jobs/openshift/open-telemetry-opentelemetry-operator/OWNERS [pavolloffay]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@pavolloffay: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

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