Andrew Sy Kim

> A kubelet can run multiple versions of K8s, there is no bug. I think you mean a kubelet is compatible with multiple versions of K8s, but a user specifying...

Sounds good, thanks for clarifying @akutz

/assign @akutz

+1 from me. It's disabled in https://github.com/kubernetes/cloud-provider-vsphere and I prefer it over holding PRs all the time.

/hold Needs decision from https://github.com/kubernetes-sigs/apiserver-network-proxy/issues/352

After having more time to think through the discussion in https://github.com/kubernetes/kubernetes/pull/73171, I think a more reasonable solution is to embed a virtual kubelet ID into the node's provider ID. Maybe...

Sorry in advance that I'm not familiar with the VK code. I think there are two ways to do this: * The provider implementation can return a VK specific [InstanceID...

Worth noting there is a work-around that I think is reasonable until there's a longer term solution for this upstream. The VK when it initializes itself can set `node.Spec.ProviderID` to...

Yes, the cloud provider implementations on the cluster

> but is there anything that can be done or easier done with vETH compared to internal ports? I'm not sure, veth pair was used simply because it's defacto standard...