Repository navigation
NO-JIRA: Establish OpenShift 4.21 as the upstream management baseline - #9635
stevekuznetsov wants to merge 1 commit into
Conversation
Set the upstream management-cluster minimum to OpenShift 4.21 or Kubernetes 1.34 and align the local and CI envtest matrices with that baseline. Update prerequisites and generated documentation while retaining downstream products and managed services as authorities for their own support commitments. This is a deliberate upstream policy and coverage change, not a claim that older OpenShift releases have left maintenance support. HostedCluster and NodePool release support remains unchanged. No runtime version rejection or workload rollout is added. Signed-off-by: Steve Kuznetsov <stekuznetsov@microsoft.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@stevekuznetsov: This pull request explicitly references no jira issue. 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. |
|
Skipping CI for Draft Pull Request. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe pull request sets OpenShift 4.21 and Kubernetes 1.34 as the starting versions for management API server compatibility. Envtest configuration now covers Kubernetes 1.34–1.36 and corresponding OpenShift versions. Documentation updates describe the support policy, prerequisites, envtest coverage, feature gate filtering, and explicit test-target requirements. Suggested reviewers: Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to The compatibility policy, documentation, and envtest matrices are aligned, with no identified merge-blocking behavior. 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stevekuznetsov The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9635 +/- ##
=======================================
Coverage 47.54% 47.54%
=======================================
Files 796 796
Lines 100027 100027
=======================================
Hits 47560 47560
Misses 49298 49298
Partials 3169 3169
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Stale PRs are closed after 21d of inactivity. If this PR is still relevant, comment to refresh it or remove the stale label. If this PR is safe to close now please do so with /lifecycle stale |
|
PR needs rebase. 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. |
What this PR does / why we need it:
Propose OpenShift 4.21 / Kubernetes 1.34 as the minimum upstream HyperShift management-cluster version, and align local and GitHub Actions envtest coverage with that policy.
This is an explicit upstream support-policy change, not merely a faster local test default and not a claim that older OpenShift versions have left maintenance support. It needs agreement from maintainers and downstream consumers before merge.
Changes:
Which issue(s) this PR fixes:
No Jira issue associated yet. Standalone policy proposal discussed while preparing #9634; no resource-policy API, CEL, or controller changes are included here.
Special notes for your reviewer:
Scope and migration: This removes default management-side coverage for OCP 4.17 through 4.20 and vanilla Kubernetes 1.31 through 1.33. Operators using older management clusters would need to upgrade before adopting an upstream build with the new baseline. Downstream products and managed services retain authority over their own support commitments; historical product-specific statements have not been silently rewritten.
Not changed: HostedCluster/NodePool minimum payload versions, supported-versions ConfigMap, CPO selection, runtime capability checks, API schemas, and workload templates. No new explicit installer/operator version rejection is introduced. Successful installation on an older cluster does not establish support. The generic single-version envtest default already uses Kubernetes 1.34.0 and is unchanged.
Motivation versus proof: Separate testing of the proposed policy CRD in #9634 found install-time CEL cost failures on OCP 4.19/4.20 binaries and passing admission on 4.21+. That is evidence of version-dependent API compatibility, not by itself authorization to drop older management support or evidence that all current HyperShift operations fail there. This PR makes the support decision explicit and independently reviewable. Until approved, it does not remove the compatibility blocker from #9634.
CI caveat: Wrapper workflows currently reference reusable workflows at @main. Pre-merge CI may therefore use the old matrix; the modified local matrices were exercised explicitly below.
Validation passed:
GOMAXPROCS=4 make test-envtest-api-all ENVTEST_JOBS=3: all six retained downstream/upstream versions passed using this standalone worktree.GOMAXPROCS=4 make lint: zero issues.make docs-aggregateandgit diff --check.make run-gitlintandgit verify-commit HEAD.Full make pre-commit and live management-cluster migration tests were not run. No runtime Go code changed. One signed-off, GPG-signed commit; keep draft pending support-policy review.
Checklist:
Summary by CodeRabbit
Documentation
Tests