Re: [sig-storage] [Requesting an exception] Kubernetes VolumeAttributesClass ModifyVolume

[Xing Yang]

Approved from sig-storage.

Thanks,

Xing

On Fri, Nov 7, 2025 at 3:11 AM 范宝发 <fanb...@gmail.com> wrote:

Hi release team, 

• Enhancement name: Kubernetes VolumeAttributesClass ModifyVolume
• Enhancement status (alpha/beta/stable): stable
• SIG: sig-storage
• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/3751
• PR #’s: https://github.com/kubernetes/kubernetes/pull/134556
• Additional time needed (in calendar days, due end of day AoE): 1 day
• Reason this enhancement is critical for this milestone: The linked PR has been approved by SIG Storage, all the codes are reviewed by SIG API Machinery, and will get a lgtm/approve label soon once some minor changes are made. This feature was promoted to stable in 1.34, but the feature gate was not locked. Since the beta group is disabled by default, after promoting a new resource type to stable, we wait for a release to gather user feedback. No issues are reported yet. We think it's safe to lock the feature gate and switch the storage version from v1beta1 to v1. We don't want to wait for the next release to do this.
• Risks from adding code late: (to k8s stability, testing, etc.): Most tasks have been completed in previous releases. In this release, we only lock the feature gate and switch the storage version from v1beta1 to v1. The existing tests cover all changes.
  
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.): No risks.

Much appreciated!

Fan Baofa

--
You received this message because you are subscribed to the Google Groups "sig-storage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-storage...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-storage/CAOOaVdKnEcHg2dvJ9xWGjE9KP5%3DXY62j2qeOpvwa-6Jfw2Fzzg%40mail.gmail.com.

[范宝发]

[Drew Hagen]

Hello! Thanks for filing the exception request.

For future reference, even though this is staying stable, we need to add the opted-in label so that the Release Team can track this through. This helps us evaluate readiness at every checkpoint and not scramble to check all criteria here at code freeze.
There are a few items that need to be caught up:

It looks like the kep.yaml needs an update to include 1.35 as the latest milestone, given that new work is being checked in now.
And given that the preferred storage version for VolumeAttributesClass is being from v1beta1 to v1, this introduces a user-facing change which requires an update to documentation. It is overdue to open the docs PR.

Any exception request on KEPs without opted-in label going forward will be rejected.

That being said, +1 from me for 1 day extension (now EOD today) on this so long as we can get all of the following done:

1. Get the code PR merged
2. Update the milestone field in kep.yaml to 1.35
3. Open a placeholder docs PR against the k8s website. Follow the steps here to open a PR against dev-1.35 branch in the k/website repo. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

If not, we'll have to target 1.36 on this.

[Ryota]

Unfortunately, the release team is REJECTING this exception request.

As discussed in the Slack thread, it would be better for all parties to delay this to v1.36, allowing more time for approvals, communication, and better tracking.

Thanks for your understanding and contributions!

Cheers,

Ryota