Move ResourceQuotaSelector out of validation

Use overridden context when determining if default namespace came from config

change sort function of scheduling queue to avoid starvation when a lot of unscheduleable pods are in the queue

export metrics from node lifecycle controller workqueues

Signed-off-by: Serguei Bezverkhi <sbezverk@cisco.com>

Move AppArmor feature-gate checking out of validation

Fix wrong completion for kubectl attach

Wait for propagation of secret deletion

Fix typos in kube-proxy

Shorten re-read period for token files to work with ProjectedTokenVolumeSource

verify gid in runasuser tests

Pass PodSandboxConfig to PullImage method in CRI

e2e: Fallback to internal IPs when using SSH in tests

kubeadm selfhosting: fix pod spec mutation for controller-manager

Fix for kubectl go-template 'eq' & 'lt' not working with integers.

kube-apiserver: test graceful shutdown

Remove generic mount validation logic during unmount and rely on CSI driver

CSI: Add test for passing Pod information in NodePublish call

Log Health Check failure at Verbosity Level - 4

Strengthen ErrorToAPIStatus against bad input

Fixes PR template

Set .spec.schedulerName to ds-controller.

Modified command line options --authentication-kubeconfig and
--authorization-kubeconfig to point out to the correct location
of the controller-manager.conf

This should fix this controller-manager crash:
    failed to get delegated authentication kubeconfig: failed to get
    delegated authentication kubeconfig: stat
    /etc/kubernetes/controller-manager.conf: no such file or directory

Related issue: kubernetes/kubeadm#1281

Updated the term master to control plane

Add kubeadm init unit test

Check PV requirements before scheduling

Increase default maximumLoadBalancerRuleCount to 250

Our default recommendation as well as our CI default is 4, so we should
be able to see the health check errors at the same level 4 itself.

Change-Id: I388f945d3522d1f63f0a85f35e765c2d4f2c548a

change sort function of scheduling queue to avoid starvation when unschedulable pods are in the queue

When starvation heppens:
- a lot of unschedulable pods exists in the head of queue
- because condition.LastTransitionTime is updated only when condition.Status changed
- (this means that once a pod is marked unschedulable, the field never updated until the pod successfuly scheduled.)

What was changed:
- condition.LastProbeTime is updated everytime when pod is determined
unschedulable.
- changed sort function so to use LastProbeTime to avoid starvation
described above

Consideration:
- This changes increases k8s API server load because it updates Pod.status whenever scheduler decides it as
unschedulable.
Signed-off-by: Shingo Omura <everpeace@gmail.com>

fix typo