[feature request] Kubernetes feature gates statistics and dashboards
- Dominant language
- Shell
- Stars
- 130
- Forks
- 57
- Avg merge
- 7d 9h
- Merged PRs (30d)
- 1
Description
There was recently a very discussion in sig-architecture mailing list about [What if we eliminate the beta stage for new features?](https://groups.google.com/g/kubernetes-sig-architecture/c/VPGTVa6m95M/m/lqAK_AmMBAAJ)
Lot of good points were raised, though it was obvious the problem is complex as it involves (at minimum) three categories of features as described by @thockin [here](https://groups.google.com/g/kubernetes-sig-architecture/c/VPGTVa6m95M/m/L-_zWJI6AQAJ)
I will be very useful to have some dashboard showing the existing feature gates states across releases that helped to do a more data driven decision.
I've created a one shot analysis [here](https://colab.research.google.com/drive/1nV_zv0mPZXinMiokrqdzB76cLOepO0H5?usp=sharing#scrollTo=YNz34t1-8ap2) but it quickly got outdated (it is from 1.29), I obtained the data with this [dirty script ](https://gist.github.com/aojea/7da734626e4a5287ff26461362db1c18) .
I think that the important fields are `FeatureGate|SIG Owner` that is 1:N to `Release|Default Value| Locked| State` (State: can be alpha, beta, deprecated, GA )
Interesting dashboards that come to mind ( these are suggestions feel free to add remove):
- Feature Gates per State per Release (allowing to filter by state) by SIG
- Features Created/Closed, bear in mind created may not be alpha, and closed may be GA or removed by SIG
- Features age per State by SIG
- Feature Time to Graduate
- New Features per SIG
- ....
Contributor guide
Assessment
This issue has not been assessed yet.