OpenShift is a fork of Kubernetes. Case in point. OpenShift has functionality called a Route. That isn't in Kubernetes. Kubernetes of course went and added something similar called ingress. This means that anytime Kubernetes does a release that RedHat has to manage merging all those changes in with their local changes that aren't part of their project. This is exactly the same sort of thing ...
Red Hat OpenShift Pipelines 1.21 (redhat.com) 2 points by 81jwbs8en | hide | past | favorite | discuss
Red Hat just hit us with 300% price increases for OpenShift across the board right after we went live in production after a little over a year of implementation.
Red Hat just hit us with 300% price increases for OpenShift across the ...
Red Hat Woos VMware Shops with OpenShift Virtualization Engine | Hacker ...
OpenShift is a fork of Kubernetes. Case in point. OpenShift has ...
Yes, I'd think Openshift with Kubevirt would be positioned to move in. Lots of Openshift in some of the sectors I've worked with so seems like a natural expansion. I forgot about MSFT's ability to bundle Hyper-V though which seems to come up in this thread a lot. Love the username.
Podman seems to have a better financial future outlook since it's subsidized by Red Hat's OpenShift strategy. Although I know Docker is the "standandard" and Podman sometimes has incompatibilities with Docker which it shouldn't have. HN folks seem to prefer Podman instead of Docker. What's the smartest choice here?