Signed-off-by: Doug Davis <dug@us.ibm.com>

Automatic merge from submit-queue

Fix use of docker removed ParseRepositoryTag() function

Docker has removed the ParseRepositoryTag() function in
leading to failures using the kubernetes Go client API.

Failure:

```
../k8s.io/kubernetes/pkg/util/parsers/parsers.go:30: undefined: parsers.ParseRepositoryTag
```

Automatic merge from submit-queue

Use cluster/log-dump.sh to collect base cluster logs in kubemark

Fixes #24415.

cc @fejta @spxtr @wojtek-t 

Automatic merge from submit-queue

RateLimitedQueue TestTryOrdering could fail under load

Remove the possibility of contention in the test by providing a
synthetic Now() function.

Fixes #24125

Automatic merge from submit-queue

added claim_binder sync period

simple addition to local-up-cluster to support pvclaimbinder-sync-period.

Automatic merge from submit-queue

Script to cache metadata requests on the jenkins master

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

Create an http server which caches most requests to the metadata server. Use special logic to cache access tokens such that the expires_on json field is correct. Add a script to simplify enabling/disabling the cache by editing `/etc/hosts`

Automatic merge from submit-queue

Using genericapiserver.NewConfig() instead of initialising Config in example apiserver

Automatic merge from submit-queue

kubenet: hook pod bandwidth resources up to shaper

@bprashanth @thockin Last bit for shaping.

Automatic merge from submit-queue

Collect and expose runtime's image storage usage via Kubelet's /stats/summary endpoint

This information is useful to users since docker images are typically not stored on the root filesystem.

Kubelet will also consume this feature in the future to decide is evicting images will help with disk usage on the nodes.

cc @kubernetes/sig-node 

Automatic merge from submit-queue

Move internal types of job from pkg/apis/extensions to pkg/apis/batch

This addressed the job part of #23216, this is still WIP. Will notify once finished. I'd like to have it in before starting working on ScheduledJob. 

@lavalamp @erictune fyi

Automatic merge from submit-queue

Use kube-system namespace

Fixes #23153.

Sadly, kube-system isn't automatically created, so people need to make
sure to create it in their turnup scripts.  Also after creating
kube-system it can take 10+ seconds for master and proxy to show up.

I tested the equivalent of these changes locally, but not these changes
themselves as I don't have a dev/build env up, so please read carefully
and maybe try them out!

Automatic merge from submit-queue

Move SSHTunneler to genericapiserver and remove federated-apiserver's dependency on pkg/master

cc @jianhuiz 

Automatic merge from submit-queue

use single writer to improve quota performance

Performance improvement is comparable to https://github.com/openshift/origin/pull/6658, though I'm getting some crazy stalls during initial calculation on master (not on this branch), so there may be an existing problem.  This implementation won't scale out quite as well, but I don't think we'll need much more for a while and this one is easier to read.

This buckets based on namespace, then bunches updates where possible to avoid request fanout, and does fast notification when it can.  It correctly handles updating multiple quota docs.

@derekwaynecarr @kubernetes/rh-cluster-infra 

Automatic merge from submit-queue

Make detect-node-names less brittle for G{C,K}E

Use the `--format='value()'` option with `gcloud compute instance-groups managed list{,-instances}` instead of `--format=yaml` with a series of `grep`s and `cut`s. This is hopefully a bit more stable.

Fixes #24120.

cc @kubernetes/sig-testing @jlowdermilk @freehan 

Automatic merge from submit-queue

rkt: Pass through os argument

This was lost in a rebase in #24496 and, while not required to build, is
required to function correctly under rkt (else panics!)

cc @yifan-gu 

Automatic merge from submit-queue

gke-large-cluster: Allow up to 1% of 1000 = 10 nodes

Per 2016/03/16 GKE release note, CreateCluster can return success with
only 99% success.

Automatic merge from submit-queue

Incorrect attribute - docs - pod-security-context

Pod definition had incorrect spelling on attribute `securityContext`
Also fixed the flow of Motivation introduction paragraph.

add image fs info to summary stats API.
Adding node e2e test for image stats.
Signed-off-by: Vishnu kannan <vishnuk@google.com>

Per 2016/03/16 GKE release note, CreateCluster can return success with
only 99% success.

Automatic merge from submit-queue

Change kubernetes-e2e-gke-large-cluster to n1-highmem-2

Automatic merge from submit-queue

Corrected format in hooks/pre-commit.

Format enhancement.

This was lost in a rebase in #24496 and, while not required to build, is
required to function correctly.

c.f. internal b/27776043

Slow down redis polling to ensure no flakiness in kubectl

Docker has removed the ParseRepositoryTag() function in
leading to failures using the kubernetes Go client API.

Lets use github.com/docker/distribution reference.ParseNamed()
instead.

Failure:

../k8s.io/kubernetes/pkg/util/parsers/parsers.go:30: undefined: parsers.ParseRepositoryTag

Use docker/distribution to parse image refs
Signed-off-by: Stef Walter <stefw@redhat.com>
 * Added files required by hack/verify-godeps.sh

Unify Streaming and normal Serializers

Remove the possibility of contention in the test by providing a
synthetic Now() function.

Pod definition had incorrect spelling on attribute `securityContext`
Also fixed the flow of Motivation intro paragraph.

Automatic merge from submit-queue

Add Subresource & Name to webhook authorizer.

Pass through the Subresource and Name fields from the `authorization.Attributes` to the `SubjectAccessReviewSpec.ResourceAttributes`.

Automatic merge from submit-queue

Add Services to Load test

Automatic merge from submit-queue

Refactor image related functions to use docker engine-api

ref #23563 

Hopes can do some help, cc @Random-Liu 

If it's ok, will add more work here.

Automatic merge from submit-queue

rkt: Return `FinishedAt` for pod

This is implemented via touching a file on stop as a hook in the systemd
unit. The ctime of this file is then used to get the `finishedAt` time
in the future.
In addition, this changes the `startedAt` and `createdAt` to use the api
server's results rather than the annotations it previously used.

It's possible we might want to move this into the api in the future.

Fixes #23887


I did the following manual testing:
```
$ cat ./examples/output/exit-output.yml 
apiVersion: v1
kind: Pod
metadata:
  labels:
    name: exit
  name: exit-output
spec:
  restartPolicy: Never
  containers:
    - name: exit
      image: busybox
      command: ["sh", "-c", "echo Exiting in 60; sleep 60; echo goodbye"]
$ kubectl create -f ./examples/exit/exit-output.yaml
$ # wait
$ kubectl describe pod exit-output | grep State -A 4
    State:		Terminated
      Reason:		Completed
      Exit Code:	0
      Started:		Tue, 19 Apr 2016 13:23:13 -0700
      Finished:		Tue, 19 Apr 2016 13:24:13 -0700
$ kubectl logs exit-output
Exiting in 60
goodbye
```

I double checked as well that the file at `/var/lib/kubelet/pods/$id/finished-$id` existed and looked as expected.

This is related to https://github.com/coreos/rkt/issues/1789#issuecomment-207111814 and follows https://github.com/kubernetes/kubernetes/pull/24367 + https://github.com/coreos/rkt/issues/2445

cc @jonboulle @iaguis @yifan-gu @kubernetes/sig-node