Private AI agents have been deployed securely and integrate smoothly with observability tools
What is our primary use case?
I'm changing to AI, so I'm implementing platforms for agents, specifically for artificial intelligence and agentic platforms.
It is to deploy agents in a sovereign and private tenant. Basically, when customers don't like to share their information with any cloud provider, they prefer to keep the information local. So they deploy their own private cloud, and most of them are using Red Hat OpenShift.
What is most valuable?
I find support for Kubernetes and security are the most useful features in Red Hat OpenShift.
What I appreciate from Red Hat OpenShift is the capacity to provide an integrated and secure environment that is more or less better than creating the environment from scratch or based on standard Kubernetes. Red Hat OpenShift provides a lot of features that help us to operate the platform in a very professional and efficient way, instead of using low-level tools provided with the open-source capacities. For us, it is a very practical environment in which we can quickly develop features—not using directly AI capacities from Red Hat OpenShift, but our own capacities, in a very integrated way.
The main benefits Red Hat OpenShift provides for me as a final user include the capacity to integrate third-party tools and also the integration between observability, security, and monitoring capacities.
What needs improvement?
Red Hat OpenShift is very expensive. I am starting to evaluate the capacities specifically related to artificial intelligence. The suite also integrates a lot of open source, which is more or less aligned with my strategy that always tries to use open source. However, as far as I know, it's not so flexible using the components by themselves, but I don't really have firsthand experience. That's what I've been told by the people working with them. It's not so flexible, but you win in integration and lose a little in the capacity of flexibility or making your platform more flexible.
For how long have I used the solution?
I've been working with Red Hat OpenShift for maybe one year.
What do I think about the stability of the solution?
I rate the stability of Red Hat OpenShift as quite robust. I'm satisfied with it.
What do I think about the scalability of the solution?
From one to ten, I would rate the ability to scale as nine.
How are customer service and support?
I would also rate the technical support from Red Hat as nine.
Which solution did I use previously and why did I switch?
I no longer use VMware and Tanzu data solutions because I changed my profile and my department.
How was the initial setup?
For us, the initial setup for Red Hat OpenShift is complex. It's complex, but also powerful.
What about the implementation team?
In my case, I directly work with Red Hat for purchasing the license.
What was our ROI?
Overall, I would give Red Hat OpenShift a final mark of nine.
Which other solutions did I evaluate?
As a competitor to Red Hat OpenShift, I think Rancher may be a possibility, but it's very, very far from what Red Hat OpenShift provides. I don't really know any other commercial distribution of Kubernetes. The alternative would be to create the cluster by yourself, using the components or the open-source components, but it would be really, really complicated. Also, alternatives in cloud exist, using the Kubernetes services from cloud providers like Fargate or AKS. But I would rather prefer to create Red Hat OpenShift on top of the cloud instead of using it. It's more expensive, obviously, but we have good experiences.
What other advice do I have?
In terms of functionality, I'm working with Red Hat OpenShift in terms of infrastructure and monitoring, so in these capacities, we are very satisfied.
I can recommend it to other users. Overall, I would give Red Hat OpenShift a final mark of nine.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
OpenShift Delivers Enterprise-Grade Kubernetes Without the Chaos
What do you like best about the product?
OpenShift stands out because it delivers Kubernetes without the chaos. It smooths over many of the sharp edges of upstream K8s and packages them into opinionated, enterprise-grade automation that’s built to hold up in real production use.
What do you dislike about the product?
It’s Kubernetes… plus a lot of Red Hat opinions. OpenShift’s guardrails are great... until they aren’t.
What problems is the product solving and how is that benefiting you?
It provides a complete, supported, enterprise platform with predictable lifecycle, support SLAs, and integrated tooling.
Solid Security, Steep Learning Curve
What do you like best about the product?
I really appreciate Red Hat OpenShift for its strong security features. It delivers security by default through restricted security policies and non-root containers, which reduce risk without requiring extra setup. The RBAC (Role-Based Access Control) model is clear and practical, making it easy to control who can deploy, manage, or access resources and clearly separate admin, DevOps, and developer responsibilities. We use OpenShift on a daily basis for running and managing production workloads, and features like automated scaling, rolling updates, health checks, and image scanning help us meet enterprise security and compliance needs. While the initial setup requires Kubernetes knowledge, the guided installation, good documentation, and Red Hat support make implementation manageable. Integration with existing tools like CI/CD, monitoring, and identity providers is straightforward, and Red Hat’s customer support is responsive and reliable when issues arise. Overall, it feels like a secure, well-governed platform that still keeps things simple for our team.
What do you dislike about the product?
One drawback of Red Hat OpenShift is that it can feel heavy and complex compared to plain Kubernetes, especially for smaller teams or simple workloads. The learning curve is steeper due to OpenShift-specific concepts like Routes and Operators. Also, upgrades require careful planning. The initial setup of Red Hat OpenShift was moderately complex, and while the installation process is well-documented, it still requires solid Kubernetes and infrastructure knowledge. For experienced teams, it's manageable, but for a smaller team, it feels heavy.
What problems is the product solving and how is that benefiting you?
Red Hat OpenShift solves day-to-day problems by reducing operational complexity in Kubernetes, meeting enterprise security, and compliance requirements with features like RBAC and image scanning. It ensures consistent experiences, offers automated scaling and health checks, and provides a secure platform with strong default security.
Modernization to secure microservices has improved uptime and observability for critical apps
What is our primary use case?
My main use case for Red Hat OpenShift is that we had several security tools that we deployed to Red Hat OpenShift platform, specifically when we were migrating our applications from monolithic architecture to microservices, and our OpenShift platform was using some of the AWS VMs as master and worker nodes, so it was completely on AWS, and we actually set it up from scratch, setting up those projects to be used for our applications and then deploying them with Red Hat OpenShift version 4, which we started using five years back, as it was the latest at that point in time, and then we continued to operate and run our applications there.
A quick, specific example of an application I deployed on Red Hat OpenShift is a banking-based application which we moved from a monolithic architecture to a microservices architecture, and we completely deployed it end-to-end, split into 10 plus microservices, and then it was deployed to Red Hat OpenShift platform 4.
What is most valuable?
The best features that Red Hat OpenShift offers in my experience include being a pre-assembled product where Red Hat actually makes choices for you, which for example, as a CloudOps Engineer, means I don't have to explicitly go into CLI because the web-based UI is simple and helpful for debugging, and they've integrated the logging of the application within Red Hat OpenShift. I really appreciate the automated updates, built-in observability comes with pre-configured Prometheus and Grafana stack for monitoring our cluster health, and the native tooling it has such as Red Hat OpenShift GitOps, which is a Red Hat supported Argo CD, and the integration into clusters are based on role-based access control with security by default, where Red Hat OpenShift is quite secure out of the box, having those strict permissions and using Security Context Constraints, and especially the immutable OS and Red Hat OpenShift virtualization, which is something that is really helpful.
Red Hat OpenShift has positively impacted my organization primarily through observability, as for us, application uptime matters a lot when providing public-facing products consumed by customers, and hence, we're using that to keep refining our application and products through observability metrics and keeping pace with market trends, as we promised 99.99% uptime to our customers, and the observability in Red Hat OpenShift is really helping us a lot with that.
What needs improvement?
Areas where Red Hat OpenShift can be improved include the licensing being a bit complex and maybe expensive, as that is something in the hands of the organization's higher management, especially when those licensing agreements are done, and I think Red Hat OpenShift is quite resource-heavy because the control plane and default monitoring stack consume significant resources, meaning for small clusters, a large percentage of compute goes just to running Red Hat OpenShift itself, not our apps.
For how long have I used the solution?
I have been using Red Hat OpenShift for close to six years across those different organizations.
What do I think about the stability of the solution?
Red Hat OpenShift is stable in my experience.
What do I think about the scalability of the solution?
Red Hat OpenShift's scalability is really good.
How are customer service and support?
Customer support is really good because so far in our case, we have always received a prompt response, and they have been really helpful to us. I would rate the customer support a 10 out of 10.
Which solution did I use previously and why did I switch?
We did not use any other solution before Red Hat OpenShift.
How was the initial setup?
Red Hat OpenShift is deployed in my organization on AWS.
What was our ROI?
We have saved a lot of time with Red Hat OpenShift.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing would suggest that it was more into a high cost, but then again, I'm an engineer, so this is taken care of by the higher management, and I don't have any definitive answer.
Which other solutions did I evaluate?
We did not evaluate any other solution before choosing Red Hat OpenShift because we wanted to use a licensed product for Kubernetes that has enterprise support.
What other advice do I have?
I would rate Red Hat OpenShift a 9 out of 10 overall. I choose a nine for Red Hat OpenShift because for such kind of tools, there is always room for improvement, as I already mentioned the things that can be improved in my previous answer. I would suggest that it's quite better if you're using Red Hat OpenShift for an enterprise solution, as it's really better to have the enterprise support which Red Hat OpenShift offers, and it's easy to use for Kubernetes-based applications.
Fantastic Dashboard, Needs Resource Optimization
What do you like best about the product?
I appreciate the fantastic dashboard offered by Red Hat OpenShift. Its intuitive design places all necessary functions in one location, creating an unparalleled user interface that simplifies orchestration tasks significantly. No other orchestration solution provides such a comprehensive and user-friendly console, making Red Hat OpenShift stand out in terms of usability and accessibility for managing deployments effectively.
What do you dislike about the product?
I find Red Hat OpenShift to be a bit costly, and it requires a lot of resources to start the deployment process. Additionally, the initial setup took some time to understand and get started with.
What problems is the product solving and how is that benefiting you?
I use Red Hat OpenShift to simplify application deployment with auto-scaling, resource management, and orchestration, making operations efficient.
All-in-One Platform That Streamlines Kubernetes Workflows
What do you like best about the product?
I like how OpenShift bundles everything into one clean, integrated platform. It cuts the usual Kubernetes chaos and gives teams a smoother, more reliable path from code to production.
What do you dislike about the product?
ChatGPT said:
OpenShift can feel heavy and overly strict. It demands more resources than you’d expect, and its opinionated setup sometimes slows you down when you just want to get work done.
What problems is the product solving and how is that benefiting you?
It simplifies running Kubernetes by giving a secure, stable, all-in-one platform. It reduces tool sprawl, avoids constant configuration headaches, and helps teams deploy apps faster without fighting the infrastructure every day.
Effortless Kubernetes Monitoring with OpenShift
What do you like best about the product?
What I appreciate most about OpenShift is that it serves as an advanced, out-of-the-box solution for monitoring our Kubernetes cluster. The range of options available for managing and viewing information is extensive, and the interface is very straightforward to use.
What do you dislike about the product?
One aspect I dislike about Openshift is that it does not offer straightforward support for ingress. Instead, it uses what it calls "routers," which are essentially just HA Proxy processes. I am not sure about SSO integration of Openshift, but it should be available.
What problems is the product solving and how is that benefiting you?
In my opinion, OpenShift has greatly streamlined the container orchestration process for Kubernetes. Few products offer the same combination of detail and user-friendly experience that OpenShift provides.
Openshift for data platform
What do you like best about the product?
Automating deploys of applications using helm charts
What do you dislike about the product?
Setting up authentication using htpasswd
What problems is the product solving and how is that benefiting you?
Long wait times to deploy a demo and test environment
Easiest platform to get started with, and to scale with your need
What do you like best about the product?
As a Red Hat partner, the ease of getting started with OpenShift makes it the perfect platform to bring to new and existing customers for modernizing their existing workload, or to deploy new cloud/native apps to.
What do you dislike about the product?
The continuing and never ending changing in subscriptions (CPU core count), and different products (OCP, Kubernetes engine, Virtualization etc) can make it extremely hard to predict how its going to be prices when its time to renew.
What problems is the product solving and how is that benefiting you?
OpenShift is the perfect platform for a "any cloud, anywhere, and on-prem" platform. Build in tools like s2i and gitops makes it the perfect self/service platform to developers.
Expanded the capacity to deploy applications
What do you like best about the product?
OpenShift pipelines improve the deployment capability of applications
What do you dislike about the product?
update process slow and problematic
What problems is the product solving and how is that benefiting you?
orchestration
