Red Hat is pretty good at being Red Hat
OpenShift is a fork of Kubernetes.  Case in point.  OpenShift has functionality called a Route.  That isn&#x27;t in Kubernetes.  Kubernetes of course went and added something similar called ingress.<p>This means that anytime Kubernetes does a release that RedHat has to manage merging all those changes in with their local changes that aren&#x27;t part of their project.<p>This is exactly the same sort of thing that RedHat does with their Linux kernels.  It&#x27;s exactly why you RHEL has been such a terrible platform to run Docker on.  Because RedHat is only pulling in some of the upstream changes into their kernels rather than upgrading everything.<p>This sort of merging is slow, error prone and costly.  If you use anything that they&#x27;ve added that isn&#x27;t in the upstream it creates vendor lock-in.  Sure OpenShift&#x27;s Route code is open source, but you can&#x27;t take that to any other vendor without building everything yourself.  Want that new feature in the latest Kubernetes release, you better be prepared to wait.<p>As time goes on it will become harder and harder for them to maintain this fork.  If OpenShift doesn&#x27;t become the dominate Kubernetes distribution then RedHat may lose interest in it and then you&#x27;ll lose your maintenance of that fork.  For that matter, if RedHat loses the maintainers as employees they may lose their ability to maintain this fork.<p>It&#x27;s my opinion that anyone buying OpenShift is playing with fire.<p>The fact that RedHat has failed to get their modifications integrated upstream and have to maintain themselves is a massive failure on their part.  This sort of thing was understandable in the past, but we really should expect more of them now.