The Red Hat model only worked for Red Hat
modern redhat --and this cannot be stressed enough-- is nothing like old redhat despite IBM&#x27;s fervent insistance after the acquisition they would remain hands off.<p>The hat killed Centos because some IBM midlevel manager needed to make quota for a bonus, and they didnt stop to realize just how unsuccessful this tactic was for Oracle&#x2F;MySQL.<p>moderen redhat is carved into about 40 seperate repositories and channels for packages designed to fleece you right down to the last RPM.  need Ansible? sure it comes with redhat 9.  need posix acl support from galaxy?  that&#x27;s another repo you didnt pay for.  same goes for about a hundred other packages.<p>redhat might have had great tech support in the past, but put a ticket in now and you&#x27;re in IBM levels of &quot;prove it&quot; hell with SOSReport zips and zoom screenshares until your entry level support guy gives up the ghost and calls a developer, who tells you the bug cant&#x2F;wont be fixed because libraries are hard or a rebase is impossible or any other number of boilerplate excuses why this ancient 4.x kernel based distro cant just source its solutions from fedora <i>like they said they do</i><p>and the flagships? forget it.  Yeah Quay exists but try to implement it and youll find cool stuff like an administrator account defined in configuration but not created. once created in the admin panel youll have to go back and disable new user creation so you can control user creation at all, and the whole thing just feels rickety and poorly designed from the get-go.  none of this is mentioned in the docs overtly, but is buried in Redhats bloated docs pages.  just buy a quay hosted whatever from the hat instead.<p>Openshift is equally appalling as its a massive ecosystem Redhats done virtually everything to control and nothing to distribute or competently document.  its painfully obvious IBM wants you to hire a consultant to build and deploy it...There is an open-source offering, but it cant be easily rolled into an airgap installation and it suffers the same level of byzantine and poorly written documentation as Quay.  K3S&#x2F;RKE2 easily beat it for nearly every use case.<p>Then theres the docker fiasco which unsurprisingly neither of these juggernauts wanted to deal with the others bullshit so now dockers broken in all but the most monied instances of IBM hardware.  redhat became so absolutely resolute about podman being &quot;everything you can do i can do too&quot; that it has a fucking compose option to translate docker compose into podman because people like compose but rewriting your appstack to pods when you dont want to be arsed with k8s is sort of a non-starter.