Re: Revisit feature gate graduation states for your SIG(s)

[Sergey Kanzhelev]

Thank you for bringing it. In SIG Node we are reviewing those each release and I placed it into Jan meeting agenda to try to find volunteers.

/Sergey

On Fri, Dec 19, 2025 at 11:17 AM Jack Francis <jackf...@gmail.com> wrote:

Thanks for driving visibility of this, dims!

I'll unstick HPAScaleToZero, it has an interesting backstory (feature landed in 1.16, corresponding KEP landed in 1.35, wheeeeee) It's on the agenda for the first SIG Autoscaling call after the holidays:

- https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w

Happy New Year, everyone!

Jack

On Friday, December 19, 2025 at 5:51:47 AM UTC-8 dav...@gmail.com wrote:

Hi SIG Chairs, Leads, Approvers, Contributors!

Just as we wrapped 1.35 and the master branch is open for 1.36, I wanted to put this in front of you for your planning meetings.

Please review the latest auto-generated/updated markdown for the feature gate states, There are new scripts that generate/update/verify this markdown file:

https://github.com/kubernetes/kubernetes/blob/master/test/compatibility_lifecycle/reference/feature_list.md

More importantly please carefully review the feature gates for the SIGs you are involved in and see if we can move the needle on moving things from Alpha->Beta->GA. Please update the KEPs and/or issues with any blockers on progress etc. 

Thanks,

Dims

PS: Some quick stats and highlights. Also if you see if any of the data or visualization is wrong, we can fix it up, the code for maintaining the markdown is checked into k/k already.

  | Category                     | Count                                       |
  |------------------------------|---------------------------------------------|
  | Total Feature Gates          | 214                                         |
  | Stuck in Alpha (6+ versions) | 16                                          |
  | Stuck in Beta (8+ versions)  | 13                                          |
  | Oldest stuck feature         | 24 versions (QOSReserved, Alpha since 1.11) |

  Top 10 Most Stuck Features:

  | Feature                        | Stage | Since | Versions Stuck |
  |--------------------------------|-------|-------|----------------|
  | QOSReserved                    | Alpha | 1.11  | 24             |
  | RotateKubeletServerCertificate | Beta  | 1.12  | 23             |
  | CustomCPUCFSQuotaPeriod        | Alpha | 1.12  | 23             |
  | StorageVersionHash             | Beta  | 1.15  | 20             |
  | APIResponseCompression         | Beta  | 1.16  | 19             |
  | HPAScaleToZero                 | Alpha | 1.16  | 19             |
  | StorageVersionAPI              | Alpha | 1.20  | 15             |
  | GracefulNodeShutdown           | Beta  | 1.21  | 14             |
  | CSIVolumeHealth                | Alpha | 1.21  | 14             |
  | PodDeletionCost                | Beta  | 1.22  | 13             |

--

Davanum Srinivas :: https://twitter.com/dims

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/73c07931-2413-449b-8357-ec78f86b468dn%40googlegroups.com.

[Hemant Kumar]

Thanks for bringing this up.

sig-storage is actively working to find best way to move forward with CSI volume health. We are planning another alpha of the feature in v1.36. We had decent bit of discussion during v1.35 release cycle about this feature - https://docs.google.com/document/d/1kyp7MYzwpzarzuH8spVZURc-izP0NJGRKw4bpXMjWmk/edit?tab=t.0#heading=h.3e8yz5b5vsn2 and how to move forward.

We still have to keep this in alpha though, because this time we are proposing concrete API objects to represent volume's health. 

You received this message because you are subscribed to the Google Groups "sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-node+u...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-node/CA%2Bsr0%2BCLTzjqPXfpZ7yUF5Z7RO4efTR2H2b1xa%2BpkGd%3D_dZSiQ%40mail.gmail.com.