5 ms·
well the problem with openshift on redhat/centos/atomic/whatever is that you still need to regulary update your cluster os's. however when you setup a bootkubed
by merb 9y ago
well the problem with openshift on redhat/centos/atomic/whatever is that you still need to regulary update your cluster os's.
however when you setup a bootkubed/self-hosted kubeadm cluster you can basically run on coreos and only need to update your self-hosted control plane and kubelet/(etcd, if not self hosted, too) this makes it way, way easier to have an up-to-date os + kube than any other solution (kubelet and etcd can be updated via etcd-wrapper and kubelet-wrapper, so this is even more insane).
BUT i think that red hat pushes for an easier upgrade path anyway, that's why they basically bought coreos. for CoreUpdate + Tectonic + MatchBox, so I think that in the end Redhat will have a similar simplier upgrade mechanism, but only time will tell.
What would in fact be awesome if CoreUpdate could also update Kubernetes Kubelet's and Etcd and than it would be a no-ops os if something broke you just boot a new system and delete the broken node.
And yes kubectl is the ssh/ftp of k8s. https://www.youtube.com/watch?v=07jq-5VbBVQ https://www.youtube.com/watch?v=07jq-5VbBVQ
- oblio 9y agoIsn't there also Rancher in this space? https://rancher.com/rancher2-0/ https://rancher.com/rancher2-0/
- snuxoll 9y agoYou 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 agoBut 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 agoI'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 agoWould this work? https://github.com/philips/ansible-kubernetes-daemonset https://github.com/philips/ansible-kubernetes-daemonset