Stephen Augustus
Stephen Augustus
We're going to be moving `kubernetes-cni` into the `kubelet` package. I should be able to wrap this up in 1.18. /milestone v1.18 ref: https://groups.google.com/d/topic/kubernetes-sig-release/yhf7hAqJEN0/discussion
SIG Network (@kubernetes/sig-network-misc) -- Who are the best owners for the "CNI plugins maintainers" tasks listed in the issue description? /assign @thockin @dcbw @caseydavenport /remove-priority important-soon /priority critical-urgent
FYI @huchengze @ydcool (ref: https://github.com/kubernetes/kubernetes/issues/87228#issuecomment-580330485)
> Btw. I'm also interested in that who should be notified on kubernetes side in case of creating new release of cni plugins, as week ago I didn't had this...
I've opened a corresponding issue for the CNI plugins maintainers tasks in their repo: https://github.com/containernetworking/plugins/issues/446
PR to bundle CNI plugins in the kubelet apt/yum packages: https://github.com/kubernetes/release/pull/1309
Putting this back in progress. Hoping to close the books on this in v1.20.
/remove-priority critical-urgent /priority important-soon /remove-lifecycle rotten
/assign @Verolop
@cpanato -- can you give this a rebase?