Auto commit by PR queue bot

Use JENKINS_PUBLISHED_VERSION instead of JENKINS_USE_RELEASE_TARS and JENKINS_USE_STABLE

Bring up a 4000 node kubemark cluster in Jenkins.

This is a bit of a hack of the existing scripts, but the quickest way to get this cluster up.
Will restructure e2e.sh to do this in a more sane way in a separate PR.

Use strong type for container ID

unset Kubelet flag for manifest_url for master node.

Move the hooks section to the commit section.

Updated doc for cluster autoscaler

Demo a sidecar mode within pod for java users

Add an example demonstrating runtime constraints

include name match in mischeduled check in daemonset controller

fix master swagger spec

Add unit tests for deployment controller

Bump fsouza/go-dockerclient

Change all references to the container ID in pkg/kubelet/... to the
strong type defined in pkg/kubelet/container: ContainerID

The motivation for this change is to make the format of the ID
unambiguous, specifically whether or not it includes the runtime
prefix (e.g. "docker://").

Kubelet sets kernel overcommit_memory flag

Add major- and minor-pinned latest.txt and stable.txt release publications

Auto commit by PR queue bot

Auto commit by PR queue bot

Add PodSecurityContext and backward compatibility tests

Experimental Cluster Autoscaler configuration object

Revert "Allow specifying scheme when proxying"

Change logging in scheduler_predicates e2e test

Fixed flaky cluster size autoscaling e2e.

Tweak limits for system pods in manifest files.

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot