Exception request: Kubelet CRI graduation

[Elana Hashman]

• Enhancement name: Kubelet CRI graduation
• Enhancement owner: @mrunalp @saschagrunert (Sascha is OOO for the rest of the week so I've picked this up on his behalf)
  
• Enhancement status (alpha/beta/stable): Beta
  
• SIG: Node
  
• k/enhancements repo issue #: #2040: https://github.com/kubernetes/enhancements/issues/2040
  
• PR #’s: https://github.com/kubernetes/kubernetes/pull/106501
  
• Additional time needed (in days): Until the end of the week (11/19); PR was approved and ready to go on 11/15 until we realized there was a missing, critical unit test. Due to time zone constraints and OOO, we barely missed the merge window. The follow-up PR should be fully approved by EOD (11/17).
  
• Reason this enhancement is critical for this milestone: We announced the deprecation of the v1alpha2 CRI about a year ago; delaying the move to v1 a release will further delay the removal of the old CRI. We need to graduate CRI support in order to remove Dockershim next release.
  
• Risks from adding code late: (to k8s stability, testing, etc.) The v1 CRI is byte-for-byte identical to the v1alpha2 CRI, and the implementation we use performs an unsafe cast (verified for safety with unit tests) to avoid any performance constraints when falling back to the old version. Containerd currently only supports the v1alpha2 CRI version. However, we were able to verify in presubmits that it works as expected, so we do not anticipate any additional risks for merging this late.
  
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.) This may potentially delay the Dockershim removal; we need the CRI to be fully graduated to v1 so that end users can confidently migrate.
  

[Rey Lejano]

Hi Elana,

Thank you for creating this exception request to Code Freeze until the end of this week, Fri, Nov 19. With the required approval and we recognize the importance of this enhancement to graduate CRI support, we APPROVE this request. Please have the k/k PR and follow-up PR approved and merged by Friday.

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

Thank you,

Rey Lejano

1.23 Release Team Lead

--
To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.