Dr. Stefan Schimanski

Thinking about non-rc pods, one could leave them running and force the admin to decide. Depending on the environment this could even be configurable. We could even add some label/annotation...

Also note that the controller keeps running, i.e. keeps watching the nodes and pods with old executor ids. This means the admin can manually kill non-rc pods and the controller...

There is no communication other than the annotations done by the scheduler. So the controller keeps running, watching the nodes for that annotation. No need to shut it down.

in fact it's pretty similar to the node controller. the node controller watches nodes and checks the status updates. If there is none for some time, it will kill all...

@jdef how do you see the config objects in relation to this ticket? As far as I can judge with my limited knowledge of the config object road ahead, some...

Have you seen the upstream plan how the kubelet will react on config changes? Will it just shutdown or will it try to apply changes in-place?

If we can read the config object from the scheduler, pass it down to the executor and kubelet, we would be able to determine compatibility. A look at the kubelet...

The subcommand works with TLS. What is missing is a way to tell it about a custom certificate.

In fact, the cert in the subcommand has nothing to do with the kubernetes certs. The apiserver is behind the admin router and that brings its own (snakeoil-) cert. 2016-01-20...

Look at my code to check certificates in the subcommand. It just reads the settings in the dcos.toml and applies them to kube/config. Am Donnerstag, 21. Januar 2016 schrieb James...