Files

Dr. Stefan Schimanski 67746908e5 Deleting gracefully terminating, not-scheduled pre-scheduled pods

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.

2015-09-26 23:42:08 +02:00

completions/bash

move daemonset describe to experimental

2015-09-22 09:13:42 -07:00

for-tests

netexec shellCommand endpoint returns the error if shell command fails, instead of killing netexec

2015-09-21 16:32:51 -07:00

mesos

Deleting gracefully terminating, not-scheduled pre-scheduled pods

2015-09-26 23:42:08 +02:00

README.md

add readme to redirect people to new repo

2015-08-13 17:53:12 -07:00

README.md

Kubernetes Contrib is moving!

Checkout https://github.com/kubernetes/contrib for anything that is missing here!