Automatic merge from submit-queue

Add Persistent Volume E2E in the context of a disrupted kubelet

This PR adds a test suite for persistent volumes affected by a disrupted kubelet.  Two cases are presented:

1.  A volume mounted via PVC remains accessible after a kubelet restart.
2.  When a pod is deleted while the kubelet is down, the mounted volume is unmounted successfully.

Automatic merge from submit-queue

Add default imagePullPolicy for initContainers.

fixes #38542

Merge pull request #36221 from pospispa/86-5-add-checks-and-documentation-about-template-pods-for-recycling

Automatic merge from submit-queue (batch tested with PRs 37959, 36221)

Recycle Pod Template Check

The kube-controller-manager has two command line arguments (--pv-recycler-pod-template-filepath-hostpath and --pv-recycler-pod-template-filepath-nfs) that specify a recycle pod template. The recycle pod template may not contain the volume that shall be recycled.

A check is added to make sure that the recycle pod template contains at least a volume.

cc: @jsafrane

Automatic merge from submit-queue

Add ready replicas in Deployments

Fixes https://github.com/kubernetes/kubernetes/issues/28381

@kubernetes/deployment PTAL

Automatic merge from submit-queue

Extend logging in restore-from-backup script

Automatic merge from submit-queue

Copy workqueue to client-go

The workqueue is very useful when building controllers, so this PR copied it to client-go's staging area.

Fix https://github.com/kubernetes/kubernetes/issues/33497

Update generated for 2017

Automatic merge from submit-queue

Kubelet: add image ref to ImageService interfaces

This PR adds image ref (digest or ID, depending on runtime) to PullImage result, and pass image ref in CreateContainer instead of image name. It also

* Adds image ref to CRI's PullImageResponse
* Updates related image puller
* Updates related testing utilities

~~One remaining issue is: it breaks some e2e tests because they [checks image repoTags](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/util.go#L1941) while docker always returns digest in this PR. Should we update e2e test or continue to return repoTags in `containerStatuses.image`?~~

Fixes #38833.

Automatic merge from submit-queue

cluster/gce: Rename coreos to container-linux.

Since coreos distro has been be renamed to container linux, we need to follow the naming convention here as well.

We also need to rename the libvirt-coreos as well, but to make review easier, that will happen in another PR.

cc @euank @philips

Run hack/verify-flags-underscore.py -e > hack/verify-flags/exceptions.txt

Automatic merge from submit-queue

Curating Owners: pkg/genericapiserver

cc @lavalamp @smarterclayton @nikhiljindal

In an effort to expand the existing pool of reviewers and establish a
two-tiered review process (first someone lgtms and then someone
experienced in the project approves), we are adding new reviewers to
existing owners files.


If You Care About the Process:
------------------------------

We did this by algorithmically figuring out who’s contributed code to
the project and in what directories.  Unfortunately, that doesn’t work
well: people that have made mechanical code changes (e.g change the
copyright header across all directories) end up as reviewers in lots of
places.

Instead of using pure commit data, we generated an excessively large
list of reviewers and pruned based on all time commit data, recent
commit data and review data (number of PRs commented on).

At this point we have a decent list of reviewers, but it needs one last
pass for fine tuning.

Also, see https://github.com/kubernetes/contrib/issues/1389.

TLDR:
-----

As an owner of a sig/directory and a leader of the project, here’s what
we need from you:

1. Use PR https://github.com/kubernetes/kubernetes/pull/35715 as an example.

2. The pull-request is made editable, please edit the `OWNERS` file to
remove the names of people that shouldn't be reviewing code in the
future in the **reviewers** section. You probably do NOT need to modify
the **approvers** section. Names asre sorted by relevance, using some
secret statistics.

3. Notify me if you want some OWNERS file to be removed.  Being an
approver or reviewer of a parent directory makes you a reviewer/approver
of the subdirectories too, so not all OWNERS files may be necessary.

4. Please use ALIAS if you want to use the same list of people over and
over again (don't hesitate to ask me for help, or use the pull-request
above as an example)

Automatic merge from submit-queue

Ssh fix

**What this PR does / why we need it**:
Use the dial timeout provided by the SSH library to prevent the dangling connections.

fixes #33472

**Special notes for your reviewer**:
I did not set the TCP Timeout or Deadlines. That will take more work but wasn't sure if it is needed. More importantly, I wasn't sure what values we would want to use.

Automatic merge from submit-queue

create psp policy in local-up-cluster.sh

run the command
```
PSP_ADMISSION=true ALLOW_PRIVILEGED=true ALLOW_SECURITY_CONTEXT=true ALLOW_ANY_TOKEN=true ENABLE_RBAC=true RUNTIME_CONFIG="extensions/v1beta1=true,extensions/v1beta1/podsecuritypolicy=true" hack/local-up-cluster.sh
```
create psp policies for rbac

Automatic merge from submit-queue

Remove all MAINTAINER statements in the codebase as they are deprecated

**What this PR does / why we need it**:
ref: https://github.com/docker/docker/pull/25466

**Release note**:

```release-note
Remove all MAINTAINER statements in Dockerfiles in the codebase as they are deprecated by docker
```
@ixdy @thockin (who else should be notified?)

- Update bazel for new vendored crypto

Automatic merge from submit-queue

bump gazel: pick up some new unit tests

Automatic merge from submit-queue (batch tested with PRs 39307, 39300)

kubenet: define KubenetPluginName for all platforms

This PR moved KubenetPluginName to a general file for all platforms.

Fixes #39299.

cc/ @yifan-gu @freehan

Automatic merge from submit-queue

Remove build containers

Automatic merge from submit-queue

Remove kube-up for vsphere

**What this PR does / why we need it**:
Kube-up for vSphere does not work in master or 1.5 branch due to changes in networking model within kubernetes.
Kube-up is deprecated
Kube-up for vSphere is not being maintained instead the focus is on kubernetes-anywhere.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: 
fixes https://github.com/kubernetes/kubernetes/issues/37150, fixes https://github.com/kubernetes/kubernetes/issues/36440, fixes https://github.com/kubernetes/kubernetes/issues/27947, fixes https://github.com/kubernetes/kubernetes/issues/24407, fixes https://github.com/kubernetes/kubernetes/issues/22390, fixes https://github.com/kubernetes/kubernetes/issues/14368, fixes https://github.com/kubernetes/kubernetes/issues/14363, fixes https://github.com/kubernetes/kubernetes/issues/3630, fixes https://github.com/kubernetes/kubernetes/issues/22885


**Special notes for your reviewer**:

This is related to https://github.com/kubernetes/kubernetes.github.io/pull/2021

**Release note**:

```release-note
Remove the deprecated vsphere kube-up.
```

5 containers are created during the build and not used anymore. Removing them.

Automatic merge from submit-queue

Added e2e test for HA master that creates multizone workers.