Exception request for KEP-4988: Snapshottable API server cache

60 views
Skip to first unread message

Marek Siarkowicz

unread,
Feb 14, 2025, 12:51:39 PMFeb 14
to kubernetes-sig...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com, David Eads, Joe Betz
  • Enhancement name: Snapshottable API server cache
  • Enhancement status (alpha/beta/stable): Alpha
  • SIG: api-machinery
  • k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/4988 
  • PR #’s: N/A for enhancement freeze
  • Additional time needed (in days): 0, KEP in implementable state is merged and approved by leads. We just forgot the "lead-opted-in" label.
  • Reason this enhancement is critical for this milestone: Reliability improvement by reducing memory needed to serve large LIST responses and improves APF request cost estimates 
  • Risks from adding code late: N/A for enhancement freeze.
  • Risks from cutting enhancement: N/A for enhancement freeze

    KEP in implementable state was approved by SIG lead and merged yesterday, issue was just not marked with the "lead-opted-in" label.


David Eads

unread,
Feb 14, 2025, 1:17:57 PMFeb 14
to Marek Siarkowicz, kubernetes-sig...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com, Joe Betz
I agree with this exception.  One of our tech leads was out sick and I forgot to set the label.  The design and PRR were agreed and merged before the deadline.
Reply all
Reply to author
Forward
0 new messages