CSI is used by both the kubelet and kube-controller-manager.  Both
components will initialize the csiPlugin with different VolumeHost
objects.  The csiPlugin will then assign a global variable for
the node info manager.  It is then possible that the kubelet gets
the credentials of the kube-controller-manager and that will cause
CSI to fail.

Proxy settings may interfere with a kubelet client communicating with
the API server, so set the proxy to nil.

Both SharedIndexInformer and threadSafeMap were changed to allow
AddIndexers to be called after a start or items are in the cache. While a
new Indexer is being added handling deltas is blocked in the informer.
When a new Indexer is added to a cache with existing items all indices
are recalculated.

One point to note is that adding a new indexer on a started informer
will case all indexes to be rebuilt, but it will not trigger an
updateNotification.  This is done because it is impractical to assume
any existing ResourceEventHandler would have knowledge of a yet to be
added index. Any ResourceEventHandler that would need to consume this
new index should be added after the new Indexer is added.

The "none" driver is expected to be used in "rootless" mode until OCI/CRI runtime
get support for cgroup2 (unified) mode with nsdelegate.

Even after cgroup2 gets supported in the ecosystem, the "none" driver will remain
because nested containers might not always get support for cgroup2 (via systemd).
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

# Conflicts:
#	cmd/kubelet/app/server.go
#	pkg/features/kube_features.go

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

Update golang/x/net dependency on release-1.15

Merge pull request #81520 from cblecker/automated-cherry-pick-of-#81390-#81489-upstream-release-1.15

Update release-1.15 to go 1.12.9

Automated cherry pick of #80176: Make kubelet report usageNanoCores for node on Windows

The port name previously didn't matter on these tests, but is now
actively being checked in go1.12.8 and higher.

https://github.com/golang/go/commit/3226f2d492963d361af9dfc6714ef141ba606713

Manual cherry pick of #80978 upstream release 1.15

Automated cherry pick of #81279: Fix Azure client requests stuck issues on

Update the Windows node image 1809 version to 0709