Automated cherry pick of #72259 upstream release 1.13

Automated cherry pick of #72344: Fix create secret docker-registry compatibility

storage_scheduling: retry operation as intended

Automated cherry pick of #72361 upstream release 1.13 

Automated cherry pick of #71895 #72106 upstream release 1.13

Automated cherry pick of #72291: Check for volume-subpaths directory in orpahaned pod

Automated cherry pick of #71834 upstream release 1.13

Automated cherry pick of #72081: Make scheduleinternalcache.PodFilter as public

Automated cherry pick of #71992: fix race condition when attach azure disk in vmss

cherry pick #72135 to 1.13: Surface selected pod RuntimeHandler in Kubelet logs

Automated Cherry Pick of #71581 to release-1.13

Automated cherry pick of #59525: fix node and kubelet start times

Automated cherry pick of #71990: fix kubelet log flushing issue in azure disk

update cloud provider boilerplate

Add a test that reproduces the race condition between setting nominated node name of a pod and scheduling cycle of other pods

The pull-kubernetes-verify presubmit is failing on
verify-cloudprovider-gce.sh because it is a new year and thus current
test generated code doesn't match the prior committed generated code in
the copyright header.  The verifier is removed in master now, so for
simplicity and rather than fixing the verifier to ignore the header
differences for prior supported branched, this commit is the result of
rerunning hack/update-cloudprovider-gce.sh.
Signed-off-by: Tim Pepper <tpepper@vmware.com>

Fixes #72163

Automated cherry pick of #72035 and #72084: bump golang to 1.11.4 (CVE-2018-16875)

Automated cherry pick of #72030: Fix race condition when joining nodes

Automated cherry pick of #72123: kubeadm: fix nil check in join config creation

Automated cherry pick of #71945: kubeadm: fixed etcd sync endpoints

fix gofmt issue

Ensure volume mount error checking is done inside the operation so that
failures get handled with exponential backoff, etc.

Despite we were checking for the kubelet kubeconfig file to be present, the
kubelet first writes this file and then the certificates the kubeconfig file
refers to. This represents a race condition in kubeadm in which when we confirm
that the kubelet's kubeconfig file is present we continue creating a clientset
out of it. However, the clientset creation will ensure that the certificates the
kubeconfig file refers to exist on the filesystem.

To fix this problem, not only wait for the kubelet's kubeconfig file to be
present, but also ensure that we can create a clientset ouf of it on our polling
process, while we wait for the kubelet to have performed the TLS bootstrap.