I'm genuinely interested why you believe this is the case. Can you point to anything in specific about the converged stack that makes you feel uneasy? From the CoreOS perspective, OpenShift will literally become the new version Tectonic, which was work from before the acquisition, but with the ability to install additional OpenShift components as optional Operators.

The move to Fedora on its a huge negative from my perspective. If you're just dropping OpenShift and rebranding Tectonic as OpenShift, I guess that's ok, but I'm still stuck dealing with RedHat (the organization) which in my 20+ years of being a Linux user has largely been more negative than positive.

The tooling to create the immutable image is what is changing from Mantle (our Gentoo and ChromeOS toolchain) to Fedora tools. From the consumer perspective, you will not see any RPMs or package managers in our distribution. If you have not built a custom image of Container Linux yourself, you weren't even aware this software existed.

It is to move our technology stack forwards. Container Linux and Tectonic have technology which the RH container stack has lacked (e.g. Ignition, Operator-based host upgrades). At the same time, there's tech in Atomic/Openshift which hasn't been available in the CoreOS stack, like rpm-ostree and S2I. We're really trying to do a "best of both" with the new projects.

Of course, you may disagree with what's "best". You know where to reach me (Josh Berkus) if you want to send backchannel feedback.