[do-not-merge] serverless operator periodic upgrade tests

[simkam]

test only

Summary by CodeRabbit

Tests

• Added new weekly automated testing for Knative Serverless operator upgrades with OLM v1 on OpenShift 4.21-techpreview. The test suite validates upgrade paths using complete operator dependencies and production configurations, ensuring upgrade reliability and compatibility.

[simkam]

/hold

[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: 7287a8c1-216d-46e2-b558-7f12f030e71d

📥 Commits

Reviewing files that changed from the base of the PR and between 5b3095d and f068308.

📒 Files selected for processing (2)

• ci-operator/config/openshift-knative/serverless-operator/.config.prowgen
• ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.21-techpreview.yaml

---

Walkthrough

Adds scheduled test job olmv1-operator-upgrade for OLM v1 operator upgrade testing to the 4.21-techpreview Prow pipeline with AWS cluster configuration and Slack reporting registration.

Changes

OLM v1 Operator Upgrade Test Job

Layer / File(s)	Summary
Job Registration ci-operator/config/openshift-knative/serverless-operator/.config.prowgen	Added olmv1-operator-upgrade to slack_reporter.job_names for Slack failure notifications.
Job Configuration ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.21-techpreview.yaml	New scheduled test olmv1-operator-upgrade runs make test-upgrade on a weekly cron, shares AWS/OLM v1 environment with olmv1-operator-e2e, depends on all operator images, and executes the openshift-e2e-aws workflow.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 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 describes the main change: adding periodic upgrade tests for the serverless operator, which is directly reflected in the configuration file modifications.
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 contains CI configuration changes only (YAML and markdown), not Ginkgo test code. Custom check for Ginkgo test name stability is not applicable to CI config files.
Test Structure And Quality	✅ Passed	PR contains only CI infrastructure configuration files (Prow job configs, YAML ci-operator configs). No Ginkgo test code is present in this PR, so the test quality check is not applicable.
Microshift Test Compatibility	✅ Passed	PR modifies only CI configuration files (Prowgen and ci-operator YAML), not Ginkgo test code. No It(), Describe(), Context(), etc. are added. Check not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI configuration files, not Ginkgo test code. The check specifically applies to new Ginkgo e2e tests and is not applicable here.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only CI configuration files (Prowgen and CI-operator configs) for periodic test jobs. No deployment manifests, operator code, or workload scheduling constraints are introduced.
Ote Binary Stdout Contract	✅ Passed	PR only modifies CI/CD configuration files (.config.prowgen and YAML). No executable code or process-level code is added. The OTE stdout contract check doesn't apply to configuration files.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only adds CI/CD job configurations, not new Ginkgo test code. Custom check targets e2e test implementations. Not applicable to this PR.

_{✏️ 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-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: simkam
Once this PR has been reviewed and has the lgtm label, please assign maschmid for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift-knative/serverless-operator/OWNERS

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

[openshift-ci]

@simkam: The following test 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/generated-config	f068308	link	true	/test generated-config

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.