Mike Brown

I'll do that.. start with the other packages and come back..

> Ufr, spdy, remotecommand, ... Those are huge nod.. and split up across k8s.io/* .... /kubelet, /apimachinery, /utils, /client-go, ...

for these utility net apis.. when I look at containerd/containerd/vendor for use of these two util packages I see lots of things that I'll have to dig into like: https://github.com/containerd/containerd/blob/main/vendor/k8s.io/client-go/transport/transport.go#L353...

> > one of N PRs to clean up / eliminate our k8s.io vendor impact to only external apis that carry no k8s.io internal baggage like the min golang version...

> If I'm reading @mikebrow's comment correctly, the critical issue is the one described in [kubernetes/kubernetes#130799](https://github.com/kubernetes/kubernetes/issues/130799): the minimum Go version. Importing libraries from the Kubernetes project which do not enforce...

> So the hope to eliminate all dependencies and only depend on proto files? If we HAVE TO keep one dependency, is it worth changing others? with respect to CRI...

> ok, got it. Is there an issue on k/k tp discuss not enforcing the min go version on some staged repos? we discussed it in london 1/1 with tim/liggit.....

> So basically the k/k is not changing how staging repos deal with min go version and the proposal is to move anything containerd wants to use into an independently...

/cc @cpuguy83 @kevpar @kiashok could use some help with the windows implementation..

it went into "main" on 11/20.. so missed the 2.0.0 branch.. if needed in a released branch will need to cherry pick it to the needed release branches. Otherwise it...