CONSOLE-5209: Add periodic jobs for IngressComponentRouteLabels promotion#81895
CONSOLE-5209: Add periodic jobs for IngressComponentRouteLabels promotion#81895jhadvig wants to merge 1 commit into
Conversation
…re gate 16 periodic jobs covering all required platforms (AWS HA, AWS SNO, Azure, GCP, vSphere, Baremetal IPv4/IPv6/Dual) in both Default and TechPreviewNoUpgrade variants. Interval set to 168h (weekly) initially, will be lowered to 24h once tests stabilize. Required for promoting IngressComponentRouteLabels from TechPreview to Default per the feature-zero-to-hero guide. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@jhadvig: This pull request references CONSOLE-5209 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 story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
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. |
WalkthroughAdds the console-operator 5.0 periodics release configuration, including image build settings, release targeting, resource requests, standard serial conformance tests, and TechPreviewNoUpgrade test variants across multiple cluster environments. ChangesConsole Operator 5.0 periodics
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@jhadvig, Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhadvig The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
`@ci-operator/config/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml`:
- Around line 183-187: Regenerate the periodic ProwJob artifacts for the 16 new
tests in the release-5.0 periodics configuration by running the repository’s
make update workflow, ensuring it produces the matching
openshift-console-operator-release-5.0-periodics.yaml job file under the
generated jobs output.
🪄 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: 6d3ab461-39b0-4220-8492-640fd722e6b7
📒 Files selected for processing (1)
ci-operator/config/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml
| zz_generated_metadata: | ||
| branch: release-5.0 | ||
| org: openshift | ||
| repo: console-operator | ||
| variant: periodics |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify generated Prow job file contains the new periodics
fd -p 'ci-operator/jobs/openshift/console-operator' -e yaml
rg -n 'ingress-component-route-labels' ci-operator/jobs/openshift/console-operator 2>/dev/null | head -50Repository: openshift/release
Length of output: 4447
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect the periodics config and generated job files for this repo/branch.
printf '\n== config file outline ==\n'
wc -l ci-operator/config/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml
sed -n '1,260p' ci-operator/config/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml
printf '\n== generated job files present ==\n'
fd -p 'ci-operator/jobs/openshift/console-operator' -e yaml | sort
printf '\n== search for matching periodics jobs ==\n'
rg -n 'periodic|ingress-component-route-labels|console-operator-release-5\.0' ci-operator/jobs/openshift/console-operator 2>/dev/null || trueRepository: openshift/release
Length of output: 14207
Regenerate the periodic ProwJob artifacts
The 16 new tests: entries in ci-operator/config/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml need matching generated jobs under ci-operator/jobs/openshift/console-operator/; make update should produce openshift-console-operator-release-5.0-periodics.yaml.
🤖 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/openshift/console-operator/openshift-console-operator-release-5.0__periodics.yaml`
around lines 183 - 187, Regenerate the periodic ProwJob artifacts for the 16 new
tests in the release-5.0 periodics configuration by running the repository’s
make update workflow, ensuring it produces the matching
openshift-console-operator-release-5.0-periodics.yaml job file under the
generated jobs output.
Source: Coding guidelines
|
@jhadvig: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Summary
Add periodic CI jobs for the
IngressComponentRouteLabelsfeature gate promotion from TechPreview to Default.16 jobs covering all required platforms per the feature-zero-to-hero guide:
e2e-aws-ingress-component-route-labelse2e-aws-techpreview-ingress-component-route-labelse2e-aws-sno-ingress-component-route-labelse2e-aws-sno-techpreview-ingress-component-route-labelse2e-azure-ingress-component-route-labelse2e-azure-techpreview-ingress-component-route-labelse2e-gcp-ingress-component-route-labelse2e-gcp-techpreview-ingress-component-route-labelse2e-vsphere-ingress-component-route-labelse2e-vsphere-techpreview-ingress-component-route-labelse2e-metal-ovn-ipv4-ingress-component-route-labelse2e-metal-ovn-ipv4-techpreview-ingress-component-route-labelse2e-metal-ovn-ipv6-ingress-component-route-labelse2e-metal-ovn-ipv6-techpreview-ingress-component-route-labelse2e-metal-ovn-dualstack-ingress-component-route-labelse2e-metal-ovn-dualstack-techpreview-ingress-component-route-labelsInterval starts at 168h (weekly). Will be lowered to 24h (daily) once tests stabilize and produce reliable results.
Dependencies
[OCPFeatureGate:IngressComponentRouteLabels]Labelsfield onComponentRouteSpecJira
https://redhat.atlassian.net/browse/CONSOLE-5209
Summary by CodeRabbit
Adds 16 weekly periodic CI jobs for
console-operatorrelease 5.0 to validate promoting theIngressComponentRouteLabelsfeature gate from TechPreview to Default across AWS, Azure, GCP, vSphere, and bare-metal IPv4/IPv6/dual-stack environments. The jobs cover standard andTechPreviewNoUpgradeconfigurations, including Metal OVN workflows, and are intended to increase to daily execution once stable.