Enhancement Exception: Kubelet Credential Provider

37 views
Skip to first unread message

Andrew Kim

unread,
Nov 6, 2020, 2:05:31 PM11/6/20
to kubernetes-sig-release, Walter Fender
Hey SIG Release,

The kubelet credential provider KEP (approved in v1.17), which we were
planning to work on for v1.20 was missing an enhancements tracking
issue. I was asked to file an official exception request from SIG
release since the issue is newly created.

Enhancement name: Kubelet Credential Provider
Enhancement status (alpha/beta/stable): alpha
SIG: cloud provider, node, auth
k/enhancements repo issue #:
https://github.com/kubernetes/enhancements/issues/2133
PR #’s: https://github.com/kubernetes/kubernetes/pull/94196
Additional time needed (in days): N/A
Reason this enhancement is critical for this milestone: required for
cloud provider extraction/migration
Risks from adding code late: N/A
Risks from cutting enhancement: N/A

Thanks,

Andrew Sy Kim

Walter Fender

unread,
Nov 6, 2020, 5:33:02 PM11/6/20
to Andrew Kim, kubernetes-sig-release
The Kubelet Credential Provider is currently the long poll in the Credential Provider Extraction effort.
If it can't go to Alpha in 1.20, it will push back the entire effort to generate a level playing field for all Cloud Providers in Kubernetes.
This work has been advertised for multiple years and this particular effort has been discussed as coming for the last 2 releases.
I think it is important that we get it into the 1.20 release.

Jeremy Rickard

unread,
Nov 6, 2020, 6:15:26 PM11/6/20
to Andrew Kim, kubernetes-sig-release, Walter Fender
Hey Andrew,

Thanks for submitting this exception request., and thanks Walter for the additional context in the reply. 

This is a bit of a weird scenario here, since we didn't have the tracking issue...so thank you for opening it. We'll APPROVE this exception request conditionally on you also updating the KEP to match the new format. We would have asked this be done during the enhancement collection phase, had this not slipped through the cracks. For this KEP, that would entail migrating to the new directory structure with the new metadata file. Since we're so late in the game, we'll help you get reviews on that as soon as you all can turn that around.

Also, please be aware that code freeze is coming up on Nov 12th!

Thanks,

Jeremy Rickard // 1.20 release lead

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CABc050G5_6yEyB07WQXea1CTUPz3yYeH%2BJj8izo6bsWXjGzfTw%40mail.gmail.com.

Andrew Kim

unread,
Nov 13, 2020, 3:12:56 PM11/13/20
to Jeremy Rickard, kubernetes-sig-release, Walter Fender
Hi folks,

Here's the updated KEP https://github.com/kubernetes/enhancements/pull/2151

Thanks,

Andrew Sy Kim
Reply all
Reply to author
Forward
0 new messages