Exception request for KEP-5116: Streaming Encoding for LIST Responses

22 views
Skip to first unread message

Marek Siarkowicz

unread,
Feb 14, 2025, 12:45:06 PMFeb 14
to kubernetes-sig...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com, David Eads, Joe Betz
  • Enhancement name: Streaming Encoding for LIST Responses
  • Enhancement status (alpha/beta/stable): Beta
  • SIG: api-machinery
  • k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5116
  • PR #’s: N/A for enhancement freeze
  • Additional time needed (in days): 1
  • Reason this enhancement is critical for this milestone: Reliability improvement by 3-9x memory improvement for apiserver when serving large LIST requests.
  • Risks from adding code late: (to k8s stability, testing, etc.): N/A for enhancement freeze
  • Risks from cutting enhancement: N/A for enhancement freeze

    Most of the implementation is ready, KEP was created to ensure agreement on testing. KEP in implementable state was approved by SIG lead and merged yesterday, issue was just not marked with the "lead-opted-in" label.

Marek Siarkowicz

unread,
Feb 14, 2025, 12:52:49 PMFeb 14
to kubernetes-sig...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com, David Eads, Joe Betz
Correction 

  • Additional time needed (in days): 1
  • Additional time needed (in days): 0, KEP in implementable state was merged and is approved by leads. We just forgot about the "lead-oped-in" label.

David Eads

unread,
Feb 14, 2025, 1:17:47 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