- 29 Sep, 2015 18 commits
-
-
Jerzy Szczepkowski authored
Fixed ignoring the rest of deployments after the first error in deployment controller & added logging of errors.
-
Filip Grzadkowski authored
e2e: RunRC wait until all pods created by RC are ready
-
Filip Grzadkowski authored
Fixed update of scale sub-resource for experimental RC.
-
Jerzy Szczepkowski authored
Fixed update of scale sub-resource for experimental RC. Resolves #14656.
-
Marek Grabowski authored
Small fixes to Kubemark scripts
-
gmarek authored
-
Tim Hockin authored
Changes to make kube-proxy userspace scale better
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Yu-Ju Hong authored
kubelet sends up status updates to flip the ready condition of a pod after the pod is already in the running state. RunRC should wait until the pod condition is ready to make sure there is no pending status update which may affect the follow-up performance test.
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
- 28 Sep, 2015 12 commits
-
-
Brendan Burns authored
-
Mike Danese authored
-
Marek Grabowski authored
Add cpu/mem reservation metrics for autoscaler in kube-up
-
Wojciech Tyczynski authored
Fix terminated pod printing in kubectl describe
-
Marcin Wielgus authored
-
Wojciech Tyczynski authored
Fixed panic in autoscaling e2e tests
-
Piotr Szczesniak authored
-
Marcin Wielgus authored
-
Wojciech Tyczynski authored
Initial Kubemark commit
-
Wojciech Tyczynski authored
Added debug logs to autoscaling_utils.go
-
Piotr Szczesniak authored
-
gmarek authored
-
- 27 Sep, 2015 2 commits
-
-
Brendan Burns authored
Disable kubelet_perf test in GKE
-
Brendan Burns authored
-
- 26 Sep, 2015 8 commits
-
-
Dr. Stefan Schimanski authored
In upstream the kubelet is responsible for all pods which have the spec.NodeName set. In Mesos we have a two-stage scheduling process: 1. pods with a pre-set spec.NodeName are still scheduled by the scheduler. 2. The kubelet will only see them when a Mesos task was started and the executor passes the pod to the kubelet. With this PR a pod with spec.NodeName which is gracefully terminated, but not yet scheduled, e.g. - because the termination happened just after creation and the scheduler was not fast enough - because the NodeSelector does not match is deleted by the Mesos scheduler.
-
jijun2 authored
-
Dr. Stefan Schimanski authored
We can assume that n != nil holds, because otherwise offers are skipped.
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
- pre-create node api objects from the scheduler when offers arrive - decline offers until nodes a registered - turn slave attributes as k8s.mesosphere.io/attribute-* labels - update labels from executor Register/Reregister - watch nodes in scheduler to make non-Mesos labels available for NodeSelector matching - add unit tests for label predicate - add e2e test to check that slave attributes really end up as node labels
-
Dr. Stefan Schimanski authored
-
Brian Grant authored
Revert "Maintain an IP address independent of the forwarding rule for…
-
Brian Grant authored
-