Automatic merge from submit-queue

Use mCPU as CPU usage unit, add version in PerfData, and fix memory usage bug.

Partially addressed #24436.

This PR:
1) Change the CPU usage unit to "mCPU"
2) Add version in PerfData, and perfdash will only support the newest version now.
3) Fix stupid mistake when calculating the memory usage average.

/cc @vishh 

Automatic merge from submit-queue

Enforce --max-pods in kubelet admission; previously was only enforced in scheduler

This is an ugly hack - I spent some time trying to understand what one NodeInfo has in common with the other one, but at some point decided that I just don't have time to do that.

Fixes #24262
Fixes #20263

cc @HaiyangDING @lavalamp

Automatic merge from submit-queue

Intial draft on SeedProvider docs

Alsa more documentation.  We need to reference the config section in the example docs.  There are multiple PRs open in those docs, so at this point I do not want to make a mess.

Let me know if there are docs standard template that will make this more pretty.

Automatic merge from submit-queue

Removing KUBE_API_VERSIONS from our test scripts

We dont need to specify them.
Its an unnecessary extra change that people have to make while adding a group.

We also need this change for ubernetes.

cc @caesarxuchao @jianhuiz 

Automatic merge from submit-queue

fix relative working dirctory of KUBE_ROOT

fix relative working dirctory of `KUBE_ROOT`, do not need to change to `KUBE_ROOT` in the first place
Signed-off-by: Crazykev <zcq8989@gmail.com>

Automatic merge from submit-queue

update gb-frontend image. New image includes the change in PR # 23381.

Update to use the gcr.io/google-samples/gb-frontend:v4 image. New image includes the change in https://github.com/kubernetes/kubernetes/pull/23381.

Automatic merge from submit-queue

Disable travis on master.

There's no need for it, and it's blocking merges. Until we've got the munger ignoring travis, this should patch the problem.

ref #24628

Automatic merge from submit-queue

WIP: Proposed new PR release note template.

Initial template proposal - needs work to coexist with labels:

## ATTENTION - Release Note ack required!

Use the below `release-note` block to explain your change.  Valid inputs include:

**"title"** - the release note is the title of the PR
**"none"** - No release note needed for this PR
_freeform text_ - Describe your change as a summarized release note

```release-note
...release-note block...
```

Second template proposal - replaces labels:

## ATTENTION - Release Note ack required!

Update the below named `release-note-needed` block to one of:

**\`\`\`release-note**
**\`\`\`release-note-action-required**
**\`\`\`release-note-none**

Then describe your change as a summarized release note within the block.

```release-note-needed
...release-note block...
`line` 2
```

Automatic merge from submit-queue

Fix a few typos in comments

Automatic merge from submit-queue

Default conversion for byte slices is incorrect

Nil slices are getting allocated, which is incorrect and changes
behavior in some cases.

   []byte(nil) -> []byte(nil)

@wojtek-t

Automatic merge from submit-queue

Fix ConfigMapList.Items to not use omitempty

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

Automatic merge from submit-queue

etcd3/watcher: cancelling context shouldn't return error

Fixes #24528

Automatic merge from submit-queue

Add timeout to e2e network connectivity checks

Some e2e tests use wget to check connectivity, and the default e2e
timeout is 900s.  This change allows the timeout to be specified on a
check-by-check basis.  This will also make the check useful for negative
checks (like those used by openshift to validate isolation) since a
short timeout is suggested where connectivity is not expected.

Automatic merge from submit-queue

jenkins: Allow configuration of release bucket

This allows others to leverage the existing E2E code to test some
patched kube binary by simply overriding the bucket and reusing many of
the existing scripts

Automatic merge from submit-queue

All clients under ClientSet share one RateLimiter.

Currently we create a rate limiter for each client in client set. It makes the reasoning about rate limiting behavior much harder. This PR changes this behavior and now all clients in the set share single rate limiter. Ref. #24157

cc @lavalamp @wojtek-t 

Automatic merge from submit-queue

Kubelet: Refactor all but image related functions in DockerInterface

For #23563.
Based on #23699 and #23844.

Only last 3 commits are new. This PR refactored all functions except image related functions, including:
* CreateExec
* StartExec
* InspectExec
* AttachToContainer
* Logs
* Info
* Version

@kubernetes/sig-node 

Automatic merge from submit-queue

node_e2e: disable serialized image pulls and increase test timeout

This addresses #24605

Automatic merge from submit-queue

disable linkcheck jenkins job

I don't have time to fix linkcheck any soon, so temporarily disable the job.

ref #23162

Automatic merge from submit-queue

Client auth provider plugin framework

Allows client plugins to modify the underlying transport to, for example, add custom authorization headers.

Automatic merge from submit-queue

Rackspace improvements (OpenStack Cinder)

This adds PV support via Cinder on Rackspace clusters. Rackspace Cloud Block Storage is pretty much vanilla OpenStack Cinder, so there is no need for a separate Volume Plugin. Instead I refactored the Cinder/OpenStack interaction a bit (by introducing a CinderProvider Interface and moving the device path detection logic to the OpenStack part).

Right now this is limited to `AttachDisk` and `DetachDisk`. Creation and deletion of Block Storage is not in scope of this PR.

Also the `ExternalID` and `InstanceID` cloud provider methods have been implemented for Rackspace.

Automatic merge from submit-queue

First pass at a GKE large cluster Jenkins job

Runs a 1000 node GKE parallel e2e test. On demand only. We'll add more
tests as I see what actually works - this is going to have some
flakiness on its own.

Automatic merge from submit-queue

Add mpio support for iscsi

This allows the iscsi volume to check if a iscsi device belongs to a mpio device
If it does belong to the device then we make sure we mount the mpio device instead of
the raw device. 
The code is based on the current FibreChannel volume support for mpio

example
/dev/disk/by-path/iqn-example.com.2999 -> /dev/sde
Then we check
/sys/block/[dm-X]/slaves/xx
until we find the [dm-X] containing /dev/sde and mount it

Additional work that can be done in future
1. Add multiple portal support to iscsi
2. Move the FibreChannel volume provider to use the code that has been extracted

Automatic merge from submit-queue

update hack/build-go to build federation/cmd/federated-apiserver as well

federation/cmd/federated-apiserver was added in https://github.com/kubernetes/kubernetes/pull/23509

cc @jianhuiz 

Automatic merge from submit-queue

fix ./cluster/kube-up.sh failed after vagrant halt. (issue #18990)

Runs a 1000 node GKE parallel e2e test. On demand only. We'll add more
tests as I see what actually works - this is going to have some
flakiness on its own.

Automatic merge from submit-queue

call genericapiserver directly instead of going via master in federated-apiserver

I can cleanup more code, but this is the minimum required to unblock https://github.com/kubernetes/kubernetes/pull/23847

cc @jianhuiz 

Automatic merge from submit-queue

Allow components to use protobufs while talking to apiserver.

Automatic merge from submit-queue

remove log spam from nodecontroller

@thockin @quinton-hoole ptal.