[k8s API machinery] Exception Request for KEP-4330

[Siyuan Zhang]

Hi everyone!

I'd like to request an exception for a KEP for 1.31.

• Enhancement name: Compatibility Versions in Kubernetes
• Enhancement status (alpha/beta/stable): alpha
• SIG: api-machinery
• k/enhancements repo issue #: 4330 (https://github.com/kubernetes/enhancements/issues/4330)
• PR #’s: https://github.com/kubernetes/kubernetes/pull/125941
• Additional time needed (in days): 6 day
• Reason this enhancement is critical for this milestone: 

Feature introduces version compatibility and emulation options to Kubernetes control plane components to make upgrades safer by increasing the granularity of steps available to cluster administrators..

• Risks from adding code late: (to k8s stability, testing, etc.)

Low risk, the main implementation for the feature has been merged early in this release cycle. The remaining PR is just a bug fix for the example apiserver and an atomic pointer.

• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

The example apiserver would not be deployable. The atomic pointer might run into race conditions in the rare use case of DeepCopying a feature gate.

Code has been reviewed several rounds at the moment. Requesting for 6 days for more back and forth for reviewer feedback.

Thank you!

Siyuan Zhang (@siyuanfoundation)

[Siyuan Zhang]

Updating the time requested to 3 days.

• Enhancement name: Compatibility Versions in Kubernetes
• Enhancement status (alpha/beta/stable): alpha
• SIG: api-machinery
• k/enhancements repo issue #: 4330 (https://github.com/kubernetes/enhancements/issues/4330)
• PR #’s: https://github.com/kubernetes/kubernetes/pull/125941

• Additional time needed (in days): 3 day

• Reason this enhancement is critical for this milestone: 

Feature introduces version compatibility and emulation options to Kubernetes control plane components to make upgrades safer by increasing the granularity of steps available to cluster administrators..

• Risks from adding code late: (to k8s stability, testing, etc.)

Low risk, the main implementation for the feature has been merged early in this release cycle. The remaining PR is just a bug fix for the example apiserver and an atomic pointer.

• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

The example apiserver would not be deployable. The atomic pointer might run into race conditions in the rare use case of DeepCopying a feature gate.

Code has been reviewed several rounds at the moment. Requesting for 3 days for a couple of rounds back and forth for reviewer feedback.

[Angelos Kolaitis]

Hi all,

The release team is APPROVING this exception request (Slack thread). Your updated deadline to merge all PRs for your KEP is 19:00 PDT Friday, 26th July 2024.

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

Thanks,
Angelos Kolaitis
1.31 Release Team Lead