Re: [atomic-devel] Introducing Commissaire

On May 19, 2016 17:03, "Jason DeTiberus" wrote: > > > > On Thu, May 19, 2016 at 4:31 PM, Jeremy Eder wrote: >> >> ​Would commissaire be intended to address the case where I want to adjust config options across a cluster? (openshift node or master configs)​

Re: [atomic-devel] Introducing Commissaire

​Would commissaire be intended to address the case where I want to adjust config options across a cluster? (openshift node or master configs)​ On Thu, May 19, 2016 at 3:57 PM, Derek Carr wrote: > Yep, definitely agreed - and it's not even implemented yet so I can't >

Re: [atomic-devel] Introducing Commissaire

Yep, definitely agreed - and it's not even implemented yet so I can't recommend people use it as a part of the overall procedure, but something to keep in mind in this problem space that this is one potential way of updating the cluster node agent and the daemons it manages in the future. On Thu,

Re: [atomic-devel] Introducing Commissaire

On May 19, 2016 2:59 PM, "Derek Carr" wrote: > > Related: https://github.com/kubernetes/kubernetes/pull/23343 > > This is the model proposed by CoreOS for supporting cluster-upgrades. Basically, a run-once kubelet is launched by the init system, and pulls down the real kubelet

Re: [atomic-devel] Introducing Commissaire

Hello thanks for releasing this blog post, from a first impression there is a bit of an overlap if you are already cloudforms to do that, isn't it ? Chmouel On Thu, May 19, 2016 at 3:55 PM, Stephen Milner wrote: > Hello all, > > Have you heard about some kind of cluster host

Re: [atomic-devel] Introducing Commissaire

Awesome! Was wondering what tools out there were for monitoring / modifying hosts that have kubernetes / openshift / etc. on them. At the moment I've been doing it manually (via ssh'ing in, etc.) I'll try this out! The *only* tool I've used in comparison to this would be docker-machine with it's