
Community insights

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.
Reviews
Videos
Red Hat OpenShift Review
Red Hat OpenShift Review
Red Hat OpenShift Review
Red Hat OpenShift Review
Use Cases and Deployment Scope
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.
A developers great journey into the world of Devops
Use Cases and Deployment Scope
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.
Red Hat OpenShift review
Use Cases and Deployment Scope
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.
Red Hat Openshift Platform.
Use Cases and Deployment Scope
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.
Red Hat Openshift on RAN.
Use Cases and Deployment Scope
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.
Red Hat OpenShift the most mature and stable Kubernetes solution on the planet
Use Cases and Deployment Scope
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.
OpenShift Review
Use Cases and Deployment Scope
Primarily right now we're doing with VMs. We were a Rev customer and migrated our Rev VM workloads to OpenShift virtualization. We also have our eye on the future with container environment, so it fits perfectly into what we were doing now and what we look to do in the future.
Pros
- It's a one pane of glass, so when we have Rev only it was a hypervisor for VMs. OpenShift, you can put Ansible in it, you can hook into satellite, it can do with OpenShift AI. You can do AI models and stuff like that. So I think it's more like a Swiss Army knife rather than a fire extinguisher.
Cons
- OpenShift virtualization has a little room for improvement. I'm coming from it as a Rev customer. There's some things in that OpenShift virtualization that were in Rev that I would like to see in OpenShift virtualization. I realized that they're chasing the VMware crowd and that's fine, but from us old Rev customers, we'd like to see some things that was in Rev around via migration and things of that nature that could be in OpenShift virtualization, I hope is being planned to be put in.
Likelihood to Recommend
Well suited if you are looking to do containers, if you're looking for an easy way to build a container platform, there's so much in it to easily do that. Right now it's not as great as handling VMs with my aforementioned comments about how it can improve. So I would say it's low point right now it's the VMs, but it looks like they're improving. But the high point is always containerization.
Top Notch PAAS Solution
Use Cases and Deployment Scope
It is one of the finest platform as a service platform. we are using this for build & deploy our application for cloud because it makes our application more secure and scalable. It has very low downtime. Customer support is fabulous. It ensure security compliance. Red Hat OpenShift has lots of inbuilt features and service that enhance productivity and scalability. It provide flexibility and more control on our application for better handling.
Pros
- Makes app more robust and scalable.
- Easy to maintain and has self recovery.
- Track & monitor issues and quick notify.
- Simple User Interface
Cons
- Complex to setup for new user.
- Less no of features as compared to other solution available in the market.
Likelihood to Recommend
It is well for us to migrating our old application on the cloud for better security and speed. Creating clusters for reducing load and enhancing experience of the application.
OpenShift Review
Use Cases and Deployment Scope
Spend less and have common platform for containers and VM
Pros
- Open
Cons
- Scale
Likelihood to Recommend
OpenShift in Platform Engineering
Use Cases and Deployment Scope
We use OpenShift within multiple departments, but in mine specifically (integrated platform engineering) we use it for running pods related to hosting web apps for publication resources, running builds, and creating ephemeral testing environments for kits. We have 2 clusters not currently in production, and are working towards that this year.
Pros
- Locked down RHCOS hosting vms
- Operators make adding major features easier
- Console is good for observability
Cons
- Docs for installation are especially rough
- Connectivity to LDAP for authentication is complex, especially for such a desirable feature
- Cluster install takes too long to be truly ephemeral
Likelihood to Recommend
OpenShift is great for our business cases, where things like security and sign ons are a major concern. We've also automated a bit of the setup ourselves to make it easier. Without the prior experience i have, however, install would be infeasible without dedicated support from RH. I would not recommend for personal / community use





