This reverts commit af8fbc32.

This reverts commit f32696e7.

This reverts commit 48d3ca23.

This reverts commit 11653b11.

Automatic merge from submit-queue

retry some operation in the gke kube-up.sh

ref https://github.com/kubernetes/kubernetes/issues/36895#issuecomment-262080246

Automatic merge from submit-queue

Add a CRI doc for developers

This doc includes basic instructions to use CRI and the current status. It does
not include the formal requirements for CRI, which should be documented
separately.

Automatic merge from submit-queue

Fixing the ingress annotation key in federated ingress controller

Fixing a few issues found during debugging https://github.com/kubernetes/kubernetes/issues/36074.

cc @kubernetes/sig-cluster-federation @madhusudancs @bprashanth

This doc includes basic instructions to use CRI and the current status. It does
not include the formal requirements for CRI, which should be documented
separately.

Automatic merge from submit-queue

Bump fluentd-es image version

New image version, containing changes from https://github.com/kubernetes/kubernetes/pull/37123 and https://github.com/kubernetes/kubernetes/pull/37219

Should be merged only after those two

@piosz

Automatic merge from submit-queue

Use netexec container in http lifecycle hook test.

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

The original test is using `"echo -e \"HTTP/1.1 200 OK\n\" | nc -l -p 1234` as a simple http server.

However, it seems that this is not very reliable, which may response before golang thinks it should.
So we get the error:
```
I1106 06:14:13.325397    2096 logs.go:41] Unsolicited response received on idle HTTP channel starting with "HTTP/1.1 200 OK\n\n"; err=<nil>
```

This PR changes the test to use the `netexec` container which is a simple http server written by golang and used in many of our networking e2e test. It should be more reliable.
Mark 1.5 since this is fixing a 1.5 release blocking issue. Mark P0 to match the original issue.

@dchen1107

Automatic merge from submit-queue

Elasticsearch data mount is chowned after container start

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

@piosz

Automatic merge from submit-queue

CRI: proposal for managing container stdout/stderr streams

This scope of this proposal is limited to the stdout/stderr logs streams of the
containers.

This addresses #30709

Adds changelog for kubedns v1.9

Automatic merge from submit-queue

Node E2E: Update ubuntu image to e2e-node-ubuntu-trusty-docker10-v2-image.

@sjenning Hopefully this will unblock  https://github.com/kubernetes/kubernetes/pull/32577.

I built a new ubuntu trusty image with docker 10 - `e2e-node-ubuntu-trusty-docker10-v2-image`. The kernel version of the new ubuntu image is `4.4.0-47-generic`.

@dchen1107 
/cc @kubernetes/sig-node 

Mark v1.5 because this unblocks a v1.5 feature https://github.com/kubernetes/kubernetes/pull/32577.

Automatic merge from submit-queue

Change stickyMaxAge from seconds to minutes, fixes issue #35677

**What this PR does / why we need it**: Increases the service sessionAfinity time from 180 seconds to 180 minutes for proxy mode iptables which was a bug introduced in a refactor.

**Which issue this PR fixes**: fixes #35677

**Special notes for your reviewer**: 

**Release note**:

``` release-note
Fixed wrong service sessionAffinity stickiness time from 180 sec to 180 minutes in proxy mode iptables.
```

Since there is no test for the sessionAffinity feature at the moment I wanted to create one but I don't know how.

Automatic merge from submit-queue

E2E tests cleanup: regexp for master replica in a separate function

Automatic merge from submit-queue

Kubemark master components run by supervisord. Try 2.

Automatic merge from submit-queue

HA master, fixed replica name when creating load balancer.

HA master, fixed replica name when creating load balancer. Was broken when replica
w/o suffix was no longer in the cluster.

E2E tests cleanup: moved generation of regexp for master replica to a separate function.

HA master, fixed replica name when creating load balancer. Was broken when replica
w/o suffix is no longer in the cluster.

Automatic merge from submit-queue

Fixed e2e tests for HA master.

Set of fixes that allows HA master e2e tests to pass for removal/addition master replicas.

The summary of changes:
- fixed host name in etcd certs,
- added cluster validation after kube-down,
- fixed the number of master replicas in cluster validation,
- made MULTIZONE=true required for HA master deployments, ensured we correctly handle MULTIZONE=true when user wants to create HA master but not kubelets in multiple zones,
- extended verification of master replicas in HA master e2e tests.

Automatic merge from submit-queue

Bump version of the fluentd-gcp image

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

Follow-up of https://github.com/kubernetes/kubernetes/pull/37123

@piosz

Automatic merge from submit-queue

test: extend time for a condition to appear in status

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

Set of fixes that allows HA master e2e tests to pass for removal/addition of master replicas.

Automatic merge from submit-queue

Remove Feature label from OutOfDisk e2e test

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

Related to https://github.com/kubernetes/kubernetes/pull/35551 and https://github.com/kubernetes/kubernetes/pull/36225

Automatic merge from submit-queue

Add more logging around Pod deletion

After this PR we'll have at least V(2) level log near all Pod deletions.

@saad-ali - this is required by GKE to help with diagnosing possible problem.

cc @dchen1107 @wojtek-t

This reverts commit a4ee3ed0, reversing
changes made to 8c90bc35.

Automatic merge from submit-queue

Check sysfs Type instead of Device

Some distribution uses "none" device to mount "sysfs" type, so kube-proxy needs to list mount points and check "types" instead of "device".

fixes #37183 

```release-note
Change sysfs mountpoint tests from Device to Type to be able to find sysfs mountpoint on "none" device
```

Automatic merge from submit-queue

Test flake: ignore dig failure; wait until timeout

The intent of this test was to continue trying until the timeout has
been reached. The extra assertion makes the test fail early when it
should not.

https://github.com/kubernetes/kubernetes/issues/37144

fix 37114

Automatic merge from submit-queue

Update the timeout in CLOSE_WAIT e2e test

I see some test flakes due to the timeout being too strict,
updating to a larger value.

Adding tail -n 1, it looks like there may be leftover state for other
runs. We really only care about one of the CLOSE_WAIT entries.

Automatic merge from submit-queue

Register api.DeleteOptions for internal batch group

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**: Registers api.DeleteOptions for internal batch group

**Which issue this PR fixes**: fixes #36806

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
Register api.DeleteOptions for internal batch group
Register api.DeleteOptions for internal autoscaling group
```

Automatic merge from submit-queue

Document config options for gcp auth provider plugin.

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:

Adds source documentation for the gcp auth provider plugin config options. Shouldn't have to read through the code to understand what the options and their defaults are.


**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
none

Automatic merge from submit-queue

Include serial port output in GCP log-dump

This should help us debug reboot failures e.g. https://github.com/kubernetes/kubernetes/issues/33882
Also useful for OOM-kill investigation.

/cc @dchen1107