ROX-29505: Remove sensor integration tests

[janisz]

• ROX-29505: run sensor integration tests only on changes #66700
• ROX-29505: run sensor integration tests on GHA stackrox/stackrox#15407

Summary

This PR removes sensor integration tests from the OpenShift CI pipeline for the StackRox project. The changes affect the CI/CD configuration across multiple branch and environment variants in the ci-operator/config/stackrox/stackrox/ directory.

Changes

The PR eliminates sensor-integration-tests (and related gke-sensor-integration-tests and merge-gke-sensor-integration-tests) test entries from CI operator configuration files covering:

• Master branch: Removes sensor integration tests from 6 variant configurations (default, ocp-4-12, ocp-4-18, ocp-4-19, ocp-dev-preview, ocp-next-candidate, ocp-stable-scanner-v4-install)
• Nightly builds: Removes sensor integration tests from 4 variant configurations (default, ocp-4-12, ocp-4-18, ocp-4-19)
• Release branch (x.y): Removes sensor integration tests and merge-related sensor test blocks from 2 variant configurations (default, ocp-4-12, ocp-4-19); additionally replaces the gke-sensor-integration-tests block with gke-nongroovy-compatibility-tests

This collectively disables the sensor integration test workflows from running in the automated CI/CD pipeline for StackRox across these different deployment configurations. The changes are coordinated with related infrastructure updates in the StackRox repository (referenced in stackrox/stackrox#15407).

[openshift-ci-robot]

@janisz: This pull request references ROX-29505 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 "5.0.0" version, but no target version was set.

Details

In response to this:

• ROX-29505: run sensor integration tests only on changes #66700
• ROX-29505: run sensor integration tests on GHA stackrox/stackrox#15407

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]

PR needs rebase.

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.

[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: cdf8f050-398e-4e2f-8bbd-eb667772aaaf

📥 Commits

Reviewing files that changed from the base of the PR and between 0528886 and 86c4149.

⛔ Files ignored due to path filters (5)

• ci-operator/jobs/stackrox/stackrox/stackrox-stackrox-master-postsubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/stackrox/stackrox/stackrox-stackrox-master-presubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/stackrox/stackrox/stackrox-stackrox-nightlies-postsubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/stackrox/stackrox/stackrox-stackrox-release-x.y-postsubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/stackrox/stackrox/stackrox-stackrox-release-x.y-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (14)

• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-18.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-19.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-dev-preview.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-next-candidate.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-stable-scanner-v4-install.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-18.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-19.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y__ocp-4-19.yaml

💤 Files with no reviewable changes (14)

• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-dev-preview.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y__ocp-4-19.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-18.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-18.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-4-19.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-stable-scanner-v4-install.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-12.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-next-candidate.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-19.yaml
• ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml

---

Walkthrough

This PR removes sensor-integration-tests entries from 14 CI operator configuration files across stackrox projects. In some files, the removed test is replaced with alternative tests or environment configurations; most changes are direct deletions from the tests matrix.

Changes

Test Suite Consolidation

Layer / File(s)	Summary
Test Entry Removal ci-operator/config/stackrox/stackrox/stackrox-stackrox-master__ocp-*.yaml, ci-operator/config/stackrox/stackrox/stackrox-stackrox-release-x.y__ocp-*.yaml, ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies.yaml, ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-18.yaml	Sensor-integration-tests test blocks are deleted from the tests configuration across multiple OpenShift versions and release variants.
Test Entry Replacement ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-12.yaml, ci-operator/config/stackrox/stackrox/stackrox-release-x.y.yaml	In ocp-4-12 nightlies config, sensor-integration-tests is replaced with operator-e2e-tests. In release-x.y config, gke-sensor-integration-tests is replaced with gke-nongroovy-compatibility-tests, and merge-gke-sensor-integration-tests is removed entirely.
Configuration Updates ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml, ci-operator/config/stackrox/stackrox/stackrox-stackrox-nightlies__ocp-4-19.yaml	Master config adds environment variables (COLLECTION_METHOD: core_bpf) to merge-gke-sensor-integration-tests postsubmit steps. Nightlies ocp-4-19 config removes sensor-integration-tests and adds ui-e2e-tests with updated OCP_VERSION.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: removing sensor integration tests across multiple CI configuration files.
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	PR modifies only CI configuration YAML files, not Ginkgo test code. No test title definitions added or modified. Check is not applicable.
Test Structure And Quality	✅ Passed	PR modifies YAML CI/CD configuration files, not Ginkgo test code. Check for test structure quality is not applicable to configuration-only changes.
Microshift Test Compatibility	✅ Passed	PR only removes existing test entries; adds no new Ginkgo e2e tests. Check applies only when new tests are added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This check applies to new Ginkgo e2e test code. The PR only removes test entries from CI configuration YAML files and does not add any new test code.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies CI-operator configuration files only, not deployment manifests, operator code, or controllers. The check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR modifies only CI configuration YAML files (not test code). The OTE Binary Stdout Contract check applies to test code modifications, not CI configuration changes. Check is not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR removes sensor-integration-tests entries from CI config files and does not add any new Ginkgo e2e tests. The custom check applies only when new tests are added, so it is not applicable.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-merge-bot]

@janisz, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto 0528886167068d0dce83b9b391a3b2a5e89cccf8 due to conflicts

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: janisz

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/stackrox/OWNERS [janisz]
• ci-operator/jobs/stackrox/stackrox/OWNERS [janisz]

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

[openshift-ci]

@janisz: 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/core-valid	86c4149	link	true	/test core-valid
ci/prow/prow-config-semantics	86c4149	link	true	/test prow-config-semantics
ci/prow/config	86c4149	link	true	/test config
ci/prow/check-gh-automation	86c4149	link	true	/test check-gh-automation
ci/prow/stackrox-stackrox-stackrox-stackrox-check	86c4149	link	true	/test stackrox-stackrox-stackrox-stackrox-check
ci/prow/owners	86c4149	link	true	/test owners

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.