Code freeze extension request for one PR for KEP-4603 Tune CrashLoopBackOff

74 views
Skip to first unread message

Laura Lorenz

unread,
Nov 7, 2024, 1:25:55 PM11/7/24
to releas...@kubernetes.io, kubernetes-sig-node, kubernetes-...@googlegroups.com
Enhancement name: Tune CrashLoopBackOff

Enhancement status (alpha/beta/stable): alpha

SIG: SIG-Node

k/enhancements repo issue #: #4603

PR #’s:  #128374, (merged: #128369,  #128356)

Additional time needed (in days): 2

Reason this enhancement is critical for this milestone: This is the first alpha to address a long standing (6 years) and highly upvoted issues in k/k, Kubernetes#57291. This enhancement was already delayed one release from missing enhancements freeze for 1.31, and with this alpha we get a discrete step forward designed to give us good signal on how to proceed with limited risk.

Risks from adding code late: (to k8s stability, testing, etc.) Low since a) this is for alpha features that are all behind alpha gates, and b) the PR is heavily reviewed and has verbal lgtm, but I am tracking down a defaulting bug in the alpha e2e which by nature is slower to run. There is a potential incoming other PR from another enhancement, concurrent with this, that may speed up those e2es, but the extra time will make it easier to simultaneously work on this with the current e2e speed and rebase on those changes if they make it.

Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.) This is the most important part of the enhancement, without this PR, there is no change to end user experience, as all other code changes this release were refactors leading up to this.

Thanks (again 😉)!
Laura

Laura Lorenz

unread,
Nov 7, 2024, 8:02:06 PM11/7/24
to kubernetes-sig-node
Update: This made it in the merge queue on time after all, thank you to Tim Allclair, Tim Hockin, and Antonio Ojea for helping me debug the tests!
Reply all
Reply to author
Forward
0 new messages