Code Freeze Exception for KEP 4960: Container Stop Signals

[Sreeram Venkitesh]

Hi folks,

I would like to request an exception for KEP 4960: Container Stop Signals.

• Enhancement name: Container Stop Signals
• Enhancement status (alpha/beta/stable): Alpha
• SIG: Node
• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/4960
• PR #’s: 
  • https://github.com/kubernetes/kubernetes/pull/130556
  • The PR is almost done, the extra time will be used for final reviews, minor refactoring and more testing.
• Additional time needed (in days): 4 days (including weekend, to merge by Monday next week)
• Reason this enhancement is critical for this milestone:
  • This KEP is in Alpha, but it involves rolling out changes in the different container runtimes in order for the feature gate to work. Delaying would mean that it would take more release cycles to roll out the feature.
• Risks from adding code late: (to k8s stability, testing, etc.):
  • Risks are minimal since this is an alpha feature and the only changes are the data sent and received in the ContainerConfig and ContainerStatus. Existing workloads should be fine.
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.):
• Since this is an opt-in feature and no other PRs have been merged, there is no risk in cutting the enhancement.

Sreeram

[nina polshakova]

Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge all PRs for your KEP is 9:00 PDT on Monday, 24th March 2025.

If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Nina Polshakova
1.33 Release Team Lead

[0] https://kubernetes.slack.com/archives/C2C40FMNF/p1742516897888209

[Nina Polshakova]

Clarification, the exception deadline is 21:00 (9:00pm) PDT.

Thanks!

Nina