1. Home
  2. Platform-as-a-Service (PaaS) Solutions
  3. Red Hat OpenShift Reviews
  4. User Review of Red Hat OpenShift
My Experience with Red Hat OpenShift
Updated June 15, 2024

My Experience with Red Hat OpenShift

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version

Microsoft Azure Red Hat OpenShift (managed)

Modules Used

  • OpenShift API Management

Overall Satisfaction with Red Hat OpenShift

We use Azure Red Hat OpenShift (ARO) to run our AAP and EDA applications. We ARO, we're able to scale up and down easily as needed, and with AAP managing over 3000 servers across multiple teams, that's a huge advantage. We are also looking into moving other Kubernetes workloads into ARO.
  • Ease of management
  • Logging
  • Auditing
  • Faster deployment
  • Slightly less confusing tables
  • More graphs
  • Though Red Hat OpenShift is fairly expense, it has actually saved us money by making it super easy to move our containerized workloads into it without any pain.
  • With it's projects (namespaces), it's easy to host multiple instances of the same application or container, but they each work individually as if they were seperate.
  • Developers find it easier to deploy and destroy their containers
We now have multiple (too many to count) CI/CD pipelines that greatly impact our ability to develop, deploy, update, and maintain our applications (at the push of a button). This gives our developers the freedom to work at their pace, and not have to wait for others to approve their containers going into the cluster.
We've not been running Red Hat OpenShift long, but I can already tell a big performance difference over our previous Kubernetes clusters. We had several weird issues in Kubernetes that we have not yet seen be an issue in Red Hat OpenShift. That alone made a world of difference to my entire organization.
They are all nice products, and they all have their place. But I'm convinced that from now on, instead of instantly just creating a Kubernetes cluster, I'm going to start seeing if Red Hat OpenShift is the best answer based on the project's overall needs. It's truly made that much of an impact on me.

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?

Yes

Did implementation of Red Hat OpenShift go as expected?

Yes

Would you buy Red Hat OpenShift again?

Yes

Red Hat OpenShift is best suited for container workloads where High Availability is of utmost importance. Between the high availability and the rolling upgrades, Red Hat OpenShift makes sense to be the top choice for those types of workloads. Red Hat OpenShift makes Kubernetes even easier to manage and administer.

Red Hat OpenShift Feature Ratings

Platform-as-a-Service
10.0
Ease of building user interfaces
10
Scalability
10
Platform management overhead
10
Workflow engine capability
10
Platform access control
10
Services-enabled integration
10
Development environment creation
10
Development environment replication
10
Issue monitoring and notification
10
Issue recovery
10
Upgrades and platform fixes
10

Using Red Hat OpenShift

10 - Mostly system administrators right now, but developers are starting to get there feet wet in the environment. We're working on getting more and more developers in there pushing their custom containers and code.
3 - As of right now, we only have 3 people internally that understand the inner workings of OpenShift, and even those 3 are still learning. We have a great Red Hat team though, and they help immensely.
  • Ansible Automation Platform
  • Event Driven Ansible
  • Developers Containers
  • We're better able to scale out when needed.
  • Our developers are loving that we now have better visibility of what their containers are doing.
  • The logging capabilities are far better than we were expecting.
  • Making applications highly available that aren't today.
  • Expand our development teams.
  • Better teach more teams about containers.
We use ARO (Azure Red Hat OpenShift) since we already have a very large Azure presence, and the process to deploy the cluster was so easy that we've already asked ourselves why we didn't use it sooner. We've struggled in the past with Kubernetes clusters that were improperly deployed by a third party, but with ARO, we're comfortable knowing it's deployed properly.