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
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
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
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
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.