Fwd: Exception Request for KEP-5365

7 views
Skip to first unread message

Drew Hagen

unread,
Nov 18, 2025, 11:21:04 AMNov 18
to sig-...@kubernetes.io, iho...@redhat.com


---------- Forwarded message ---------
From: Drew Hagen <drewha...@gmail.com>
Date: Tuesday, November 18, 2025 at 10:20:06 AM UTC-6
Subject: Re: Exception Request for KEP-5365
To: kubernetes-sig-release <kubernetes-...@googlegroups.com>


Unfortunately, the release team is REJECTING this exception request.

As mentioned in the Slack thread, exception requests must be submitted within three days after Code Freeze and Test Freeze per EXCEPTIONS.md. We've also acknowledged KubeCon NA in our Code Freeze reminder email. With the v1.35 timeline underway and the team focused on release-critical work, we’re no longer processing exceptions for this cycle.

This timing is part of the standard release cadence, even in cycles that overlap with KubeCon, and we do need to hold the line once the window closes.

Your enhancement looks great and we recommend targeting v1.36, where it can receive proper review and tracking.

Thanks for your understanding and contributions!

On Tuesday, November 18, 2025 at 4:56:29 AM UTC-6 iho...@redhat.com wrote:
Some of the final review comments by Tim Hockin (that are, by his words, "This LGTM but just tiny things") caught me right before I had to travel (a very long trip) to Kubecon. I've just returned home recently. Therefore I wasn't able to address comments in time.

However, the implementation is 99% ready and was LGMTed and approved by multiple people, leaving just "tiny" notes alongside a final LGTM.

In addition, this is an incredibly small feature with absolutely low risk.


Enhancement name: ImageVolume with an image digest
Enhancement status (alpha/beta/stable): none -> alpha
SIG: sig-node
Additional time needed (in calendar days, due end of day AoE): 2
Reason this enhancement is critical for this milestone: allows KubeVirt to replace the workaround mechanism around container disks and move to Image Volumes.
Risks from adding code late: very low. code is behind a feature gate and the feature is very small scoped.
Risks from cutting enhancement: will delay implementation by 1 quarter although implementation is practically done.

Thanks in advance.

Reply all
Reply to author
Forward
0 new messages