Skip to content

Make kueue-operator upgrade presubmit jobs optional#81490

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sohankunkerkar:kueue-upgrade-jobs-optional
Jul 6, 2026
Merged

Make kueue-operator upgrade presubmit jobs optional#81490
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
sohankunkerkar:kueue-upgrade-jobs-optional

Conversation

@sohankunkerkar

@sohankunkerkar sohankunkerkar commented Jul 6, 2026

Copy link
Copy Markdown
Member

Summary

  • Set always_run: false on all 12 upgrade e2e tests across 8 variant configs (release-1.3 and release-1.4)
  • These tests spin up AWS clusters and were running on every PR to the release branches unnecessarily
  • Tests can still be triggered on-demand via /test <name> when needed

Test plan

  • Verify upgrade jobs no longer appear automatically on PRs to release-1.3/release-1.4
  • Verify upgrade tests can be triggered manually with /test upgrade-from-4.XX-...

/cc @openshift/kueue

🤖 Generated with Claude Code

Summary by CodeRabbit

This PR updates the OpenShift CI configuration for the openshift/kueue-operator release branches so several upgrade-focused presubmit jobs no longer run automatically on every pull request.

In practical terms, the affected AWS-backed upgrade e2e and operator upgrade tests for release-1.3 and release-1.4 are now marked always_run: false, making them optional by default while still allowing manual execution with /test when needed. This reduces unnecessary CI load and avoids running expensive cluster-based upgrade checks on every PR to those branches.

Set always_run: false on all upgrade e2e tests across release-1.3 and
release-1.4 variant configs so they only run when explicitly triggered
via /test. These tests spin up AWS clusters and are expensive to run on
every PR to the release branches.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 6, 2026 14:10
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

@sohankunkerkar: GitHub didn't allow me to request PR reviews from the following users: openshift/kueue.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Summary

  • Set always_run: false on all 12 upgrade e2e tests across 8 variant configs (release-1.3 and release-1.4)
  • These tests spin up AWS clusters and were running on every PR to the release branches unnecessarily
  • Tests can still be triggered on-demand via /test <name> when needed

Test plan

  • Verify upgrade jobs no longer appear automatically on PRs to release-1.3/release-1.4
  • Verify upgrade tests can be triggered manually with /test upgrade-from-4.XX-...

/cc @openshift/kueue

🤖 Generated with Claude Code

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2026
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

An error occurred during the review process. Please try again later.

Walkthrough

This PR adds always_run: false to twelve e2e upgrade test entries across eight kueue-operator CI configuration files spanning release-1.3 and release-1.4, covering various OCP and operator version upgrade paths (4.18 through 4.22).

Changes

always_run: false additions

Layer / File(s) Summary
Release 1.3 upgrade configs
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.3__upgrade-from-4.18.yaml, ...upgrade-from-4.19.yaml, ...upgrade-from-4.20.yaml
Each single OCP upgrade e2e test entry gains an always_run: false field alongside its existing as: identifier.
Release 1.4 upgrade configs
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.18.yaml, ...upgrade-from-4.19.yaml, ...upgrade-from-4.20.yaml, ...upgrade-from-4.21.yaml, ...upgrade-from-4.22.yaml
OCP upgrade and operator upgrade e2e test entries gain always_run: false fields alongside their as: identifiers.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested labels: lgtm, rehearsals-ack

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)


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

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

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR reduces default CI load for openshift/kueue-operator release branches by making the AWS-backed upgrade presubmit jobs opt-in (manual /test …) instead of running on every PR to release-1.3 and release-1.4.

Changes:

  • Set always_run: false on upgrade presubmit jobs in the Prow job definitions for release-1.3 and release-1.4.
  • Mark the corresponding upgrade test entries in the ci-operator variant configs with always_run: false (while keeping them optional: true).

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.

Show a summary per file
File Description
ci-operator/jobs/openshift/kueue-operator/openshift-kueue-operator-release-1.4-presubmits.yaml Makes release-1.4 upgrade presubmits opt-in by setting always_run: false.
ci-operator/jobs/openshift/kueue-operator/openshift-kueue-operator-release-1.3-presubmits.yaml Makes release-1.3 upgrade presubmits opt-in by setting always_run: false.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.22.yaml Sets the upgrade test entry to always_run: false for the 4.22 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.21.yaml Sets both upgrade test entries to always_run: false for the 4.21 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.20.yaml Sets both upgrade test entries to always_run: false for the 4.20 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.19.yaml Sets both upgrade test entries to always_run: false for the 4.19 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.4__upgrade-from-4.18.yaml Sets both upgrade test entries to always_run: false for the 4.18 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.3__upgrade-from-4.20.yaml Sets the upgrade test entry to always_run: false for the 4.20 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.3__upgrade-from-4.19.yaml Sets the upgrade test entry to always_run: false for the 4.19 variant.
ci-operator/config/openshift/kueue-operator/openshift-kueue-operator-release-1.3__upgrade-from-4.18.yaml Sets the upgrade test entry to always_run: false for the 4.18 variant.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@sohankunkerkar: 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
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.21-e2e-ocp-upgrade-4-21-to-4-22-kueue-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.21-e2e-operator-upgrade-4-21-kueue-1-3-to-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.3-upgrade-from-4.20-e2e-ocp-upgrade-4-20-to-4-21-kueue-1-3 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.3-upgrade-from-4.18-e2e-ocp-upgrade-4-18-to-4-19-kueue-1-3 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.3-upgrade-from-4.19-e2e-ocp-upgrade-4-19-to-4-20-kueue-1-3 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.20-e2e-ocp-upgrade-4-20-to-4-21-kueue-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.20-e2e-operator-upgrade-4-20-kueue-1-3-to-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.22-e2e-operator-upgrade-4-22-kueue-1-3-to-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.19-e2e-ocp-upgrade-4-19-to-4-20-kueue-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.19-e2e-operator-upgrade-4-19-kueue-1-3-to-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.18-e2e-ocp-upgrade-4-18-to-4-19-kueue-1-4 openshift/kueue-operator presubmit Ci-operator config changed
pull-ci-openshift-kueue-operator-release-1.4-upgrade-from-4.18-e2e-operator-upgrade-4-18-kueue-1-3-to-1-4 openshift/kueue-operator presubmit 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.

@sohankunkerkar

Copy link
Copy Markdown
Member Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 6, 2026
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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

@kannon92 kannon92 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 6, 2026
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kannon92, sohankunkerkar

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:

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 openshift-merge-bot Bot merged commit 646e890 into openshift:main Jul 6, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants