Fix golint failures of test/e2e/framework/timer

update the dependency pmezard/go-difflib

Add server-side apply members on some apiserver OWNERS

Mark volume as in use even when node status didn't change

fix shellcheck in kube-aggregator

Fix function comment to consistent with its name

Adding a limit on the size of request body the apiserver will decode for write operations

Fix resource quota e2e test

add kustomize as a subcommand in kubectl

kubeadm cleanup: master -> control-plane

kubeadm: remove nodefs.inodesFree test defaulting on non-Linux

kubeadm: set priority class name to `system-cluster-critical` for all master components

Reduce the duration where expirationLock is held for expiration_cache

strip selected fields from managedFields

E2E storage: more tests for different pod/node combinations

Remove the deprecated `scheduler.alpha.kubernetes.io/critical-pod` pod annotation and use
the `priorityClassName` first class attribute instead, setting all master components to
`system-cluster-critical`.

discovery: speedup kubectl restmapper cache misses by a two-digit factor

kubeadm: Don't dump backtrace on reset

verify-generated-files-remake.sh: fix issues reported by shellcheck (part 2)

Fix races in scheduling queue tests

test case for shared volumes between the containers in pod

Start exporting the in-cluster network programming latency metric.

Add test files that exclude the field in question
under KubeletConfiguration -> evictionHard for non-Linux.

Add runtime abstraction for the test files in initconfiguration_tests.go

The current code logs an error and full blown backtrace if we fail to remove
the containers upon reset. This creates unneeded, huge and rather scary log
message. Fix that by leaving just the error message.
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>

The driver should support multiple pods using the same volume on the
same node.

This is a special case that both kubelet and the volume driver should
support, because users might expect it. One Kubernetes mechanism to
deploy pods like this is via pod affinity.

However, strictly speaking the CSI spec does not allow this usage
mode (see https://github.com/container-storage-interface/spec/pull/150) and
there is an on-going debate to enable it (see
https://github.com/container-storage-interface/spec/issues/178). Therefore
this test gets skipped unless explicitly enabled for a driver.

CSI drivers which create a block device for a remote volume in
NodePublishVolume fail this test. They have to make the volume
available in NodeStageVolume and then in NodePublishVolume merely do a
bind mount (as for example in
https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/pkg/gce-pd-csi-driver/node.go#L150).

Whether the read test after writing was done on the same node was
random for drivers that weren't locked onto a single node. Now it is
deterministic: it always happens on the same node.

The case with reading on another node is covered separately for test
configurations that support it (not locked onto a single node, more
than one node in the test cluster).

As before, the TestConfig.ClientNodeSelector is ignored by the
provisioning testsuite.

Fix cmd/kubelet/app lint issues

Update postprocessing_test.go