OPCT-389: doc: update version matrix and conformance suite notes for OCP 4.20+#227
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe cluster validation guide updates the OPCT/OpenShift support matrix and documents restored conformance validation support for OCP 4.20+. ChangesCluster validation documentation
Estimated code review effort: 1 (Trivial) | ~3 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
bshaw7
added
the
kind/documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@docs/guides/cluster-validation/index.md`:
- Around line 185-190: Update the “Conformance suite changes on OCP 4.20+” note
to document that OCP 4.20+ switches the Kubernetes conformance suite source from
kubernetes/conformance to kubernetes/conformance/parallel via k8s-tests-ext,
while OCP 4.19 continues using kubernetes/conformance. Retain the existing
explanation that the resulting count change is expected and not a regression.
- Around line 192-199: Update the “Validated test counts by OCP version” table
to include provenance for every OCP row, either by linking each count to its
source periodic job/run or by adding the corresponding run date. Preserve the
existing count columns while making each baseline auditable and refreshable.
🪄 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: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: 48d542ba-b7d5-40c3-955a-90a59b690775
📒 Files selected for processing (1)
docs/guides/cluster-validation/index.md
|
/lgtm |
Update the cluster validation guide to unblock VCSP validations on OCP 4.20+ and document the conformance suite fix details. Changes: - Added v0.6.5+ row supporting OCP 4.19-4.22 - Narrowed v0.6.1+ to v0.6.1-v0.6.4 (4.16-4.19) - Removed OCPBUGS-77783 blocking notice - Added info block documenting affected versions, fix availability, and references to resolved bugs Fixes: https://redhat.atlassian.net/browse/OPCT-389 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
185acb4 to
fa9b1b7
Compare
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 `@docs/guides/cluster-validation/index.md`:
- Around line 191-194: Update the “Affected versions” section to explicitly
state that OPCT v0.6.1–v0.6.4 do not support OCP 4.20+, while preserving the
existing support statements for v0.6.0 and earlier and v0.6.5+.
🪄 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: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: ec36f6a3-d337-4c46-9e64-0394c9cec0bf
📒 Files selected for processing (1)
docs/guides/cluster-validation/index.md
Address CodeRabbit review: v0.6.1-v0.6.4 also do not support OCP 4.20+, not just v0.6.0 and earlier. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vr4manta 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
|
/override e2e/e2e-cmd_adm-parse-metrics |
|
@bshaw7: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. 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 kubernetes-sigs/prow repository. |
|
/override "e2e / e2e-cmd_adm-parse-metrics" |
|
@bshaw7: Overrode contexts on behalf of bshaw7: e2e / e2e-cmd_adm-parse-metrics 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 kubernetes-sigs/prow repository. |
2 participants
Summary
Update the OPCT documentation to unblock VCSP validations on OCP 4.20+ and
address the acceptance criteria from OPCT-389.
Changes
v0.6.5+row supporting OCP 4.19-4.22 (CI workflows hardcodequay.io/opct/opct:v0.6.5)v0.6.1+tov0.6.1-v0.6.4covering 4.16-4.19openshift-tests(openshift/origin), not in OPCT or pluginsWhy v0.6.5+ and not v0.6.1+ or v0.6.6+?
OPCT_CLI_IMAGE: "quay.io/opct/opct:v0.6.5"CI note
The
e2e / e2e-cmd_adm-parse-metricstest fails on this PR due to a missingtest artifact on CloudFront (HTTP 403). This is a pre-existing infrastructure
issue unrelated to this docs-only change.
Fixes: https://redhat.atlassian.net/browse/OPCT-389
Epic: https://redhat.atlassian.net/browse/OPCT-421
Test plan
🤖 Generated with Claude Code