Skip to content

Add periodic CI cluster-updates evaluation jobs for 4.22#82093

Draft
fao89 wants to merge 1 commit into
openshift:mainfrom
fao89:cluster-update-evals
Draft

Add periodic CI cluster-updates evaluation jobs for 4.22#82093
fao89 wants to merge 1 commit into
openshift:mainfrom
fao89:cluster-update-evals

Conversation

@fao89

@fao89 fao89 commented Jul 17, 2026

Copy link
Copy Markdown
Member

Add CI configuration for cluster-updates-evals with periodic evaluation jobs for each LLM provider (OpenAI, WatsonX, Google Vertex, Google Vertex Anthropic) running daily against OCP 4.22 clusters.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

Summary by CodeRabbit

  • Adds a new CI configuration for fao89/ocp-evals to run on OCP nightly stream 4.22, including resource defaults and the lightspeed-service-api base dependency.
  • Defines four daily periodic cluster update evaluation jobs (using generic-claim) at 14:30, 15:30, 16:30, and 17:30:
    • cu-eval-openai-periodics
    • cu-eval-watsonx-periodics
    • cu-eval-vertex-gemini-periodics
    • cu-eval-vertex-anthropic-periodics
  • Each job claims an AMD64 AWS cluster, sets EVAL_TAG=cluster-updates-critical, mounts the relevant provider tokens (plus OpenAI), writes provider-specific config/system*.yaml to config/system.yaml as needed, and runs tests/scripts/test-cluster-updates.sh --artifact-dir "${ARTIFACT_DIR}" (with must-gather collection).
  • Adds/updates repo governance and Prow integration for fao89/ocp-evals: OWNERS (approver/reviewer fao89), Prow approve plugin configuration (self-approval required), Tide label gating (approved + lgtm), Slack notifications for periodic failures/errors, and trusted trigger via openshift-merge-bot.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 17, 2026
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@fao89

fao89 commented Jul 17, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

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: 860a733a-146c-44cc-9ed2-55f7b9ec3466

📥 Commits

Reviewing files that changed from the base of the PR and between da44fcd and 670b664.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/fao89/ocp-evals/fao89-ocp-evals-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (5)
  • ci-operator/config/fao89/ocp-evals/OWNERS
  • ci-operator/config/fao89/ocp-evals/fao89-ocp-evals-main__4.22.yaml
  • core-services/prow/02_config/fao89/ocp-evals/OWNERS
  • core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml
  • core-services/prow/02_config/fao89/ocp-evals/_prowconfig.yaml
🚧 Files skipped from review as they are similar to previous changes (5)
  • core-services/prow/02_config/fao89/ocp-evals/_prowconfig.yaml
  • core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml
  • core-services/prow/02_config/fao89/ocp-evals/OWNERS
  • ci-operator/config/fao89/ocp-evals/OWNERS
  • ci-operator/config/fao89/ocp-evals/fao89-ocp-evals-main__4.22.yaml

Walkthrough

Adds OCP 4.22 periodic cluster evaluation jobs for four providers and introduces repository-specific Prow ownership, plugin, trigger trust, Slack reporting, and Tide configuration.

Changes

OCP evals repository onboarding

Layer / File(s) Summary
OCP 4.22 evaluation configuration
ci-operator/config/fao89/ocp-evals/fao89-ocp-evals-main__4.22.yaml
Defines the build image, release target, resource defaults, generated metadata, and four provider-specific periodic cluster evaluation jobs.
Repository ownership and approval wiring
ci-operator/config/fao89/ocp-evals/OWNERS, core-services/prow/02_config/fao89/ocp-evals/OWNERS, core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml
Assigns repository approver and reviewer ownership and configures approval, LGTM, and trigger trust behavior.
Prow reporting and Tide policy
core-services/prow/02_config/fao89/ocp-evals/_prowconfig.yaml
Configures periodic-job Slack reporting and Tide label requirements and exclusions.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant PeriodicScheduler
  participant GenericClaimWorkflow
  participant ClusterUpdateTest
  PeriodicScheduler->>GenericClaimWorkflow: Start provider-specific periodic job
  GenericClaimWorkflow->>ClusterUpdateTest: Export settings and run test-cluster-updates.sh
  ClusterUpdateTest->>ClusterUpdateTest: Use mounted credentials and lightspeed-service-api image
Loading

Suggested labels: rehearsals-ack

🚥 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 accurately summarizes the main change: adding periodic cluster-updates evaluation jobs for OCP 4.22.
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 No Ginkgo tests were added; changed files are CI/Prow configs, and the only new names are static job identifiers.
Test Structure And Quality ✅ Passed PR only adds OWNERS/Prow/ci YAML; no Ginkgo test code or _test.go/spec files changed, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only CI/OWNERS config changed; no new Ginkgo tests or MicroShift-sensitive APIs/resources were added, so the check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests were added; this PR only adds CI/config wiring for existing cluster-updates eval jobs.
Topology-Aware Scheduling Compatibility ✅ Passed PR only adds CI/prow config and generated periodic jobs; no deployment/controller code or topology-sensitive scheduling fields were introduced.
Ote Binary Stdout Contract ✅ Passed Diff only adds OWNERS and ci/prow YAML; no main/init/TestMain code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new Ginkgo tests were added; this PR only adds CI/prow config and generated periodics, with no IPv4 assumptions or public-internet calls.
No-Weak-Crypto ✅ Passed No MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret-comparison logic appears in the added config files.
Container-Privileges ✅ Passed No privileged/hostNamespace/SYS_ADMIN/allowPrivilegeEscalation settings were added; the only root use is a standard build_root image (USER 0).
No-Sensitive-Data-In-Logs ✅ Passed No secrets or PII are committed; the configs only reference credential mount paths and a Slack channel, with no literal token values or private data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fao89

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

fao89 commented Jul 17, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-openai-periodics

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml`:
- Around line 25-180: Run make update to regenerate the downstream Prow job
definitions for the four new periodic tests—cu-eval-openai-periodics,
cu-eval-watsonx-periodics, cu-eval-vertex-periodics, and
cu-eval-vertex-anthropic-periodics—and include all generated artifacts in the
change.
- Around line 9-11: Update the Dockerfile fragment after the Git installation in
the main image build to restore the image’s standard non-root runtime user
instead of leaving USER 0 active. Add the appropriate non-root USER directive
immediately after the dnf cleanup, preserving the existing installation steps.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 48f09b52-3001-4666-874e-68ce37e75e35

📥 Commits

Reviewing files that changed from the base of the PR and between 18cd65f and 0a4383c.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (5)
  • ci-operator/config/fao89/cluster-updates-evals/OWNERS
  • ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml
  • core-services/prow/02_config/fao89/cluster-updates-evals/OWNERS
  • core-services/prow/02_config/fao89/cluster-updates-evals/_pluginconfig.yaml
  • core-services/prow/02_config/fao89/cluster-updates-evals/_prowconfig.yaml

Comment on lines +9 to +11
FROM registry.ci.openshift.org/ocp/ubi-python-311:9
USER 0
RUN dnf install -y git && dnf clean all

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.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

file='ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml'

echo "== File context =="
wc -l "$file"
sed -n '1,220p' "$file" | nl -ba | sed -n '1,120p'

echo
echo "== Search for related build-root Dockerfiles / USER instructions =="
rg -n --hidden --no-messages 'USER 0|USER 1001|build-root|dnf install -y git|FROM registry\.ci\.openshift\.org/ocp/ubi-python-311:9' ci-operator/config/fao89/cluster-updates-evals -S

echo
echo "== Nearby generated metadata / job config references =="
rg -n --hidden --no-messages 'zz_generated_metadata|periodic|presubmit|postsubmit|build_root|build-root' ci-operator/config/fao89/cluster-updates-evals -S

Repository: openshift/release

Length of output: 309


🏁 Script executed:

#!/bin/bash
set -euo pipefail

file='ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml'

echo "== Selected line ranges =="
sed -n '1,80p' "$file"
echo
sed -n '80,160p' "$file"
echo
sed -n '160,220p' "$file"

echo
echo "== Exact build-root / user references =="
rg -n '^( {2,})?(FROM|USER|RUN|build_root|build-root|dockerfile|dockerfile_literal):|USER 0|USER 1001|dnf install -y git' "$file" -n -S

echo
echo "== Other similar configs with USER restore patterns =="
rg -n 'USER 0|USER 1001|dnf install -y git' ci-operator/config -S

Repository: openshift/release

Length of output: 41037


Restore a non-root runtime user after installing Git.
ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml:9-11 leaves the build-root image running as root after dnf install. Switch back to the image’s standard non-root UID before it is used in CI.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/fao89/cluster-updates-evals/fao89-cluster-updates-evals-main__4.22.yaml`
around lines 9 - 11, Update the Dockerfile fragment after the Git installation
in the main image build to restore the image’s standard non-root runtime user
instead of leaving USER 0 active. Add the appropriate non-root USER directive
immediately after the dnf cleanup, preserving the existing installation steps.

Source: Coding guidelines

Comment thread ci-operator/config/fao89/ocp-evals/fao89-ocp-evals-main__4.22.yaml
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-openai-periodics

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-openai-periodics

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89
fao89 force-pushed the cluster-update-evals branch from 0a4383c to c883924 Compare July 20, 2026 10:54
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-openai-periodics

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-openai-periodics

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89
fao89 force-pushed the cluster-update-evals branch from c883924 to f76aba2 Compare July 20, 2026 14:30
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89
fao89 force-pushed the cluster-update-evals branch from f76aba2 to da44fcd Compare July 20, 2026 15:41
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml`:
- Around line 9-17: Update the fao89/ocp-evals plugins list to include lgtm
alongside approve so Tide can satisfy both required labels; if this
repository-level plugin list controls trigger handling, also enable the trigger
plugin.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 6ceffa54-d9db-47f2-9b43-03c2f24f0607

📥 Commits

Reviewing files that changed from the base of the PR and between f76aba2 and da44fcd.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/fao89/ocp-evals/fao89-ocp-evals-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (5)
  • ci-operator/config/fao89/ocp-evals/OWNERS
  • ci-operator/config/fao89/ocp-evals/fao89-ocp-evals-main__4.22.yaml
  • core-services/prow/02_config/fao89/ocp-evals/OWNERS
  • core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml
  • core-services/prow/02_config/fao89/ocp-evals/_prowconfig.yaml

Comment thread core-services/prow/02_config/fao89/ocp-evals/_pluginconfig.yaml
Add CI configuration for cluster-updates-evals with periodic evaluation
jobs for each LLM provider (OpenAI, WatsonX, Google Vertex, Google Vertex
Anthropic) running daily against OCP 4.22 clusters.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@fao89
fao89 force-pushed the cluster-update-evals branch from da44fcd to 670b664 Compare July 20, 2026 15:53
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

1 similar comment
@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@fao89: 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-fao89-ocp-evals-main-4.22-cu-eval-watsonx-periodics N/A periodic Periodic changed
periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-gemini-periodics N/A periodic Periodic changed
periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-openai-periodics N/A periodic Periodic changed
periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-anthropic-periodics N/A periodic Periodic changed
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-merge-bot

Copy link
Copy Markdown
Contributor

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

@fao89

fao89 commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

@fao89: 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/rehearse/periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-vertex-periodics f76aba2 link unknown /pj-rehearse periodic-ci-fao89-cluster-updates-evals-main-4.22-cu-eval-vertex-periodics
ci/rehearse/periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-gemini-periodics 670b664 link unknown /pj-rehearse periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-gemini-periodics
ci/rehearse/periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-periodics da44fcd link unknown /pj-rehearse periodic-ci-fao89-ocp-evals-main-4.22-cu-eval-vertex-periodics

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.

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant