[k8s-sig-net] Exception request for KEP-784: Kube-Proxy component configuration graduation

[Daman Arora]

Hi everyone,

I'm sorry that I missed the deadline to update the milestones before the enhancement freeze.

Thanks for the consideration

Enhancement Name:
Kube-Proxy component configuration graduation

Enhancement status (alpha/beta/stable):
alpha

SIG:
sig-network

k/enhancements repo issue #:
https://github.com/kubernetes/enhancements/issues/784

PR #’s:
https://github.com/kubernetes/enhancements/pull/4732

Additional time needed (in days):
No, the development will be done before the code freeze.

Reason this enhancement is critical for this milestone:
This long-overdue enhancement for sig-network aims to simplify the
current kube-proxy component-config, which is cluttered with various
options that are hard to specify and understand. kube-proxy being
a stable component still uses alpha configuration, this enhancement
will help in the transition towards a stable configuration.

Risks from adding code late: (to k8s stability, testing, etc.):
Since this adds a new version of the kube-proxy component-config
(optional for the consumers), there should be little risk.

Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.):
Delaying the time a user can get access to this feature

Regards,
Daman Arora
+91 9660570748

[Angelos Kolaitis]

Hi Daman,

Can you clarify how much extra time is required for this?

Thanks,

Angelos

[Angelos Kolaitis]

Hi all,

Following discussion in Slack, the release team is APPROVING this exception request.

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

Thanks,
Angelos Kolaitis
1.31 Release Team Lead