3 ms·

You already have an easy upgrade path with Atomic: atomic host upgrade - that's all it takes. As far as upgrading OpenShift itself, you already wrote the Ansib

You already have an easy upgrade path with Atomic: atomic host upgrade - that's all it takes. As far as upgrading OpenShift itself, you already wrote the Ansible inventory to deploy it (unless you're a masochist and deployed it manually) - just run the upgrade playbook against your existing inventory to upgrade to the latest point or major release. I run OpenShift Origin 3.7 on CentOS Atomic at work, in production, it's basically been set and forget - I have an ansible playbook I run once a month to do OS upgrades (have to drain pods, upgrade atomic, reboot and then allow pods back on the node and do it across all of them in sequence) and then I just run the upgrade playbook periodically as new point releases come out.

merb 9y ago
But it is still a "manual" operation, or at least a cronjobable. however with CoreUpdate it's basically automatic. No manual intervention - at least for the os part (as of now).
zwischenzug 9y ago
I'm a masochist who helps maintain this :) https://github.com/IshentRas/cookbook-openshift3 https://github.com/IshentRas/cookbook-openshift3 more seriously, we couldn't use Ansible because ssh keys are verboten where I work, and Chef is the strategic CM tool.
- philips 9y ago
  Would this work? https://github.com/philips/ansible-kubernetes-daemonset https://github.com/philips/ansible-kubernetes-daemonset