News for hackers. Stuff that matters.
Re:Kured – A Kubernetes Reboot Daemon by otterley on Thursday November 09, 2017 @07:46PM (#15667069)
Performing unattended upgrades seems like a great idea, until a bug introduced in an upgrade causes a performance or operability regression, introduces an even worse security bug, or is otherwise problematic. At worst, you could automate yourself into an outage.

IMO good reliability practices counsel against this approach, certainly not without testing these upgrades in a staging environment first.

Re:Kured – A Kubernetes Reboot Daemon by alexk on Thursday November 09, 2017 @09:20PM (#15667460)
In Telekube we have hybrid auto updates with fallback to manual in case if things go wrong, so we can recover:

https://gravitational.com/docs/cluster/#performing-upgrade

Re:Kured – A Kubernetes Reboot Daemon by otterley on Friday November 10, 2017 @12:43AM (#15668196)
How does this play out in an actual failure scenario? How can a administrator detect failures? Does it apply to the entire OS, including kernel upgrades, or just your own software?
Re:Kured – A Kubernetes Reboot Daemon by alexk on Friday November 10, 2017 @11:56AM (#15671154)
Imagine etcd or docker fails during the upgrade on one of the master nodes.

Our monitoring system - satellite will report failure to the upgrade process that will stop.

Administrator will use our diagnostic utility to diagnose the problem, fix it and proceed with upgrade from the last failed step, but in the manual mode.

> Does it apply to the entire OS, including kernel upgrades, or just your own software?

Right now it only applies to our software