Skip to content

OCPNODE-4520: Update enhancement for 5.0 GA target#2022

Open
saschagrunert wants to merge 1 commit into
openshift:masterfrom
saschagrunert:ocpnode-4520-update-enhancement-5.0-ga
Open

OCPNODE-4520: Update enhancement for 5.0 GA target#2022
saschagrunert wants to merge 1 commit into
openshift:masterfrom
saschagrunert:ocpnode-4520-update-enhancement-5.0-ga

Conversation

@saschagrunert
Copy link
Copy Markdown
Member

@saschagrunert saschagrunert commented May 26, 2026

Update the additional storage configuration enhancement to reflect
the current implementation state and 5.0 GA target.

  • Update status from provisional to implementable
  • Align API types with shipped API (StorePath type, correct struct hierarchy)
  • Document MCO :ref suffix auto-append behavior
  • Check off completed TP and GA prerequisite items (feature gate, API review, MCO, CRI-O v1.36, docs, test coverage, security review, RHOAI, field feedback, migration path)
  • Pin GA target to 5.0, add upgrade/downgrade paths
  • Strengthen experimental API risk documentation
  • Add implementation references and related JIRA issues

cc @haircommander @QiWang19 @sairameshv @harche @bitoku @yuqi-zhang

API PR: openshift/api#2858

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 26, 2026

@saschagrunert: This pull request references OCPNODE-4520 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.

Details

In response to this:

Update the additional storage configuration enhancement to reflect
the current implementation state and 5.0 GA target.

  • Update status from provisional to implementable
  • Add 5.0 GA goal (promote AdditionalStorageConfig to Default)
  • Update API types to match shipped API (shared StorePath type,
    consecutive slash validation)
  • Document MCO :ref suffix auto-append behavior
  • Check off completed TP checklist items (feature gate, API review,
    MCO implementation, CRI-O v1.36)
  • Pin GA target from 4.23+ to 5.0
  • Add GA upgrade path (4.22 to 5.0)
  • Strengthen experimental API risk documentation

cc @haircommander @QiWang19 @sairameshv @harche @bitoku @yuqi-zhang

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.

@openshift-ci openshift-ci Bot requested review from mandre and patrickdillon May 26, 2026 08:05
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme 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:

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

@saschagrunert saschagrunert force-pushed the ocpnode-4520-update-enhancement-5.0-ga branch 4 times, most recently from 2b48a50 to 800605b Compare May 26, 2026 08:37
- Update status from provisional to implementable
- Add 5.0 GA goal (promote AdditionalStorageConfig to Default)
- Update API types to match shipped API (StorePath type,
  consecutive slash validation, correct struct hierarchy)
- Document MCO :ref suffix auto-append behavior
- Check off completed TP and GA prerequisite items
- Mark CRI-O v1.36 risk as resolved
- Pin GA target from 4.23+ to 5.0
- Add GA upgrade/downgrade paths (4.22 to 5.0)
- Strengthen experimental API risk documentation
- Fix OCPNODE-4051 description to match JIRA title
- Add references for shipped implementation PRs and GA stories
- Fix field count (three, not two)

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@saschagrunert: all tests passed!

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.

@haircommander
Copy link
Copy Markdown
Member

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants