News for hackers. Stuff that matters.
Re:Roadmap for CoreOS Integration with Red Hat OpenShift by kev009 on Wednesday May 09, 2018 @12:47AM (#17027459)
The PR is written a bit ambiguously, is the Gentoo based container Linux going to be maintained or will it move to EL/Fedora?
Re:Roadmap for CoreOS Integration with Red Hat OpenShift by smarterclayton on Wednesday May 09, 2018 @01:02AM (#17027504)
Maintained. A new offering based on RHEL will be initially targeted for the supported scenarios under openshift while we work with the communities on how they want to evolve.
Re:Roadmap for CoreOS Integration with Red Hat OpenShift by merb on Wednesday May 09, 2018 @02:54AM (#17027882)
So will there be a path to upgrade CoreOS to RedHat Container Linux?
Re:Roadmap for CoreOS Integration with Red Hat OpenShift by cgwalters on Thursday May 10, 2018 @10:03AM (#17038916)
If you're using Tectonic in particular, we're certainly aiming to have a nice path. Although there are a lot of details in the term "upgrade" - it may require reprovisioning, but a lot of the idea of carrying forward Ignition is that any early OS customization you've made still applies.

If you're running a Kubernetes cluster, while Red Hat CoreOS will support automatic inplace updates just like existing CL, I'd say it's best practice to do periodic reprovisioning to flush out extra node state. For example in RHEL 7.5 we switched from devicemapper to overlayfs, but existing instances don't get automatically transitioned. If you're using k8s reprovisioning works well as all the containers just move off and then back on.