Item: Red Hat OpenShift
Rating: 10
Author: Verified User

Overall Satisfaction with Red Hat OpenShift

Use Cases and Deployment Scope

Enterprise Kubernetes offering for entire corporation.
- Multi-tenancy Innovation, Staging and Production clusters
- Self managed cluster offering where we automate cluster creation for an internal product team preconfigured with:
- Corporate governance as Code (ATO'd via IaC process)
- Common capabilities we believe every cluster/team needs

Pros and Cons

Pros

Secure by Default
Opinionated choices that marry well to our Enterprise needs
Progressive investment in upstream products when Enterprise gap exists

Cons

Documentation is basic and often lacking
Better support (and/or documentation) for Air-gapped environments
Better support (and/or documentation) for environments with custom PKI

Return on Investment

Centralized governance
App Modernization
Consistency of deployments across air gapped environments

Performance

We have not put enough load on our systems to verify but we have no reason to believe it would not handle the largest of loads by scaling horizontally.

Alternatives Considered

K3s Lightweight Kubernetes and SUSE Rancher

K3S supports constrained resource environments but does not have the governance controls needed for our company Rancher RK2 is being actively developed for constrained environments where Red Hat OpenShift is too heavy.

Key Insights

Do you think Red Hat OpenShift delivers good value for the price?

Yes

Are you happy with Red Hat OpenShift's feature set?

Yes

Did Red Hat OpenShift live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Red Hat OpenShift go as expected?

Yes

Would you buy Red Hat OpenShift again?

Yes

Other Software Used

Microsoft Visual Studio Code, Podman.io

Likelihood to Recommend

Less appropriate in resource constrained environments or hardware based deployments