TrustRadius Insights for Red Hat OpenShift are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Seamless Migration Process: Users have praised the effortless transition facilitated by Red Hat OpenShift when migrating from other hypervisors like Red Hat Enterprise Virtualization or VMware, particularly highlighting the efficiency of offline migration without disruptions. This streamlined process has been commended for minimizing downtime and ensuring a smooth shift to the new platform.
Built-in Operators: Customers appreciate the seamless experience offered by the built-in operators within Red Hat OpenShift, emphasizing their role in simplifying tasks compared to manual configuration in Kubernetes environments. The availability of these operators significantly reduces the complexity of managing workloads and enhances overall operational efficiency.
User-Friendly Interface: Reviewers find Red Hat OpenShift's user interface impressive for its intuitive design, specifically noting the ease of navigation and functionality while working directly within a web browser. The well-organized layout and accessibility of features contribute to a positive user experience, allowing users to efficiently monitor and manage their applications with ease.
We are both a user & consultants for Red Hat OPenShift. The great thing about OpenShift is that it runs on any cloud! It is also very efficient to run workloads..
Pros
Workload efficiency
Lowering Cost
Agility
Cons
Maybe Cost
Better Windows Integration
Likelihood to Recommend
We have customers looking to move away from VMware. OpenShift provides an enterprise platform for customers to use both vitalization and containers.
OpenShift brings a cloud native capabilites to our internal developments teams to allow faster deployment, and better access to a contantainer orchestration
Pros
The Ui increases adoption and promotes learning
OpenShift brings cloud tooling on premise
OpenShift has access to a wide variety of extended functionality via operators
Cons
The Add-on ACM component is not intuitive
Managing many clusters does not scale easily
Likelihood to Recommend
It's a great way to get into kubernetes and modenrn application hosting and deplpoyment
We use Red Hat OpenShift daily. It is our first option to go when we need to deploy microservices for any type of project. This give us the opportunity to have a centralized standardized way to deploy our services. It is a very strong solution in which besides working very good, have a great support and community you can trust.
Pros
Resource management
Architecture simplicity
Easy to manage
Cons
Modern UI
A defined routemap
Better init tutorial
Likelihood to Recommend
It is difficult to thing where Red Hat OpenShift can't be appropriate. In this days every software you make is a microservice that needs to be deploy in a kubernetes like solution... even when you can have a monolithic, business go with microservices. You can have others solutions but if you can afford this one. This is your goat.
As I assume for most companies using Red Hat OpenShift, we use the platform as an efficient and automating tool to manage and deploy our containerized applications across several environments. We often use Red Hat OpenShift for our Docker containers to package applications and their dependencies and monitoring their status to help us determine if any issues arise or develop from new code changes.
Pros
Great at helping develop and manage containers
Helps modernize our older applications
Gives Enterprise-Grade features needed for developming our system for our customer.
Cons
Reduce complexity for smaller teams/projects/companies
More optimization of resource consumption.
Improved debugging and troubleshooting tools.
Likelihood to Recommend
When working with containers on our system, there is multiple team members that may be changing, developing, and/or deploying containers around the same time of day. Using Red Hat OpenShift allows us to work seamlessly together. However, when it comes for simple changes/testing, I feel it is often quicker for me to work manually within the containers to then just make developments and then redeploy.
So, in my organization, we use Red Hat OpenShift as a devops container to host our applications. So every time we push a new version into our git azure, the pipeline is automatically triggered to build the new image and deploy our application. The big advantage we got from using Red Hat OpenShift is that when we used traditional virtual machines to deploy our applications, we didn't know when the service stopped and every time the VM stopped, we had to restart the application (which is essentially a .jar file) again, it didn't restart automatically. In addition, the application artifact is created manually using maven commands. Fortunately, all this was solved using Red Hat OpenShift, because in Red Hat OpenShift we just push the code to git and the magic happens automatically.
Pros
build images
deploy applications
secure applications
organize the pipeline between the source code and the deployed app
great UI to explore the status of the app: dashboarding
Cons
adding custom tasks to a predefined pipelines
simplify the access for the logs
simplify the add of custom resources (UI instead of yaml)
documentation in the yaml files
Likelihood to Recommend
Red Hat OpenShift FITS THE BILL:As a financial institution, our applications must always be up and running, because money is the most important thing to some people, and they can't forgive any delays. Red Hat OpenShift therefore gives us the ability to check the status of our applications and, most importantly, in the event of a problem, Red Hat OpenShift restarts the application automatically.Red Hat OpenShift IS LESS APPROPRIATE: when you have a small integration system, I don't think Red Hat OpenShift is the most appropriate choice, given its price and size. It's like driving a mazzarati in a crowded small town.
VU
Verified User
Engineer in Information Technology (1001-5000 employees)
It takes a lot of the headache out of deploying and scaling, and helps keep dev and prod in sync ,s ince it’s built on Kubernetes, we get all the power and flexibility of K8s, but with a much nicer experience for the teams — especially when it comes to automation, monitoring, and managing clusters
Pros
it integrates with CI/CD.
Security is also a big win.
handles multi-tenancy really well
Cons
Virtualization’s improving, but networking still feels a bit limited.
Likelihood to Recommend
works really well for large-scale container workloads and AI/ML use cases it’s solid, flexible, and production-ready. Virtualization is improving, but still needs work; recent updates look promising. For small, simple apps, it might be more than you need.
We had a business requirement to integrate multiple systems, where we had developed a large number of APIs and microservices. To manage and deploy this large number of APIs and services, we used Red Hat OpenShift as a cloud platform to host and expose our endpoints to consumers who want to use the integration flow. OpenShift provides a significant edge in managing a large number of applications, offering features such as scaling, automated deployment, integration with monitoring tools, and resource quota usage statistics.
Pros
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
Cons
It would be better to see the UI for Service Mesh enablement separately.
It can enhance the console view, which displays application logs and the status of requests.
Currently, we have a large number of APIs in a single namespace, which is difficult to view at a single point in time in OpenShift; perhaps we can see some improvement in the API lists and views.
Likelihood to Recommend
If you have a large number of APIs within your application scope, OpenShift is the platform you should use to manage all the apps with ease.
VU
Verified User
Professional in Information Technology (10,001+ employees)
Open Shift is used as part of the AI-RAN POC CaaS to evaluate the 5G functionalities and RAN capability. Orchestrating CPU and GPU resources can be a challenging problem, but the Red Hat team is willing to support and learn with us as we progress. The team has ample resources and learning materials to get us started. We appreciate the Red Hat team and their support of our multiple RAN projects.
Pros
Lot of educational materials.
Prompt responses and turn-around support.
Professional and knowledgeable people.
Local support on site when required.
Cons
Orchestration between GPU and CPU guideline.
RAN related Kubernetes orchestration examples.
Likelihood to Recommend
Red Hat's OpenShift is easy to use and offers extensive support.
VU
Verified User
Team Lead in Research & Development (501-1000 employees)
We use Red Hat OpenShift as a flexible MLOps platform through OpenDataHub, enabling streamlined model training, tracking, and deployment workflows. It serves as the backbone for our AI Inference Server, allowing us to scale and manage containerized inference endpoints efficiently. Additionally, Red Hat OpenShift hosts our IBM Qiskit development environment via JupyterHub, supporting quantum computing research and prototyping. This setup addresses challenges in deploying reproducible ML pipelines, managing compute resources, and integrating emerging technologies like quantum computing. The scope includes AI/ML development, automated deployment, and hybrid cloud scalability across our research and enterprise infrastructure.
Pros
Hosting Red Hat OpenShift AT (OpenDataHub)
LORA Training for Models
Hositng Inference Systems with MCP Connections
Running Development Pods for Research Projects
Cons
The complexity. Some errors occur of systems that cant interact with each other I even dont know run. The system is way to complex in its structure. It is not a OCP issue itself but Kubernetes. To get more adapted, it must be much more integrated and stable.
The UI is part of the Red Hat OpenShift Container Platform. It should also be on the Red Hat OpenShift Kubernetes Engine (in a simpler way)
Update Process is failing way too often. There are always issues.
The User enforcement cant be used in our environment. We need root in pods per standard. This is quite complicated in Red Hat OpenShift.
Likelihood to Recommend
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
