The primary use cases include troubleshooting issues, installation, implementation, and design.
External reviews
292 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Seamless upgrades have protected business operations and support secure, flexible deployments
What is our primary use case?
What is most valuable?
The benefits I have seen from using Red Hat OpenShift Container Platform include that it provides a seamless application business, and the business is never going to be impacted because deployments and upgrades can be completed without impacting the real business. Seamless activity can also be performed on the cluster without impacting the application.
Red Hat OpenShift Container Platform's policy-based governance has helped my organization maintain application security at scale because ACS is also there, and Red Hat is always maintaining things with hardening methods, always coming with hardened images, and we are frequently upgrading the minor and major versions, so it will be mitigated in that way.
Red Hat OpenShift Container Platform's hybrid and multi-cloud support will help to move applications, and if in the future any other platform wants to move, it is easy for the application to move from one platform to another without major impact.
Red Hat OpenShift Container Platform's auto-scaling capabilities have helped handle workload variations majorly at the HPA level at the pod level, but at the node level, we are not using the cloud mechanism, and that is why we are not enabling the node level.
Red Hat OpenShift Container Platform's developer-first workflow has contributed to enhancing my team's productivity because we have many custom scripts that give us reports of everything, ODR, and health-related things, so based on productivity, we are taking actions on that.
What needs improvement?
Red Hat OpenShift Container Platform needs some improvements, for example, in upgrade time, as normally, an extended upgrade method should be allowed, but sometimes if anyone clicks twice, it tries to upgrade the second level and gets stuck, so that area should be enhanced.
The strictness of the SSD and HDD also should be aligned, because in some environments, we cannot strictly make some rules related to HDD, since Red Hat is strictly making a rule after 4.16 to adopt SSD instead of HDD, which in some environments will not allow, so some workaround should be done on that.
Red Hat OpenShift Container Platform is the best option, but as many companies and the world are mainly looking for security purposes, the clear text format needs to be adopted instead of any third party. Red Hat has to develop its own product, as HashiCorp and CyberArk Conjur exist, but Red Hat needs to protect the clear text format because the secret should not be seen by anyone. Currently, it is a clear text method allowing anyone in the namespace to see the username and password, which should be controlled in that way.
The major improvements needed are related to upgrade time and strict rule-making.
For how long have I used the solution?
I have been using Red Hat OpenShift Container Platform for almost eight years.
Which solution did I use previously and why did I switch?
Before Red Hat OpenShift Container Platform, I also worked with OKD separately and Kubernetes.
How was the initial setup?
The initial setup for Red Hat OpenShift Container Platform is straightforward because I am using extra features like govc from VMware to update the parameters and these kinds of things, so it is easy on that, with no issues.
What other advice do I have?
I feel that the pricing of Red Hat OpenShift Container Platform depends on the salespeople, as they can decide that, with some companies giving a cheap price and others giving a high price for the same things. I would rate this product an 8 out of 10.
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.
Powerful Yet Challenging Transition
What do you like best about the product?
I like Red Hat OpenShift because we use it for deploying and managing our applications in containers, making scaling easy for us. The consistent experience across cloud, on-prem, and hybrid environments is really valuable, as code works the same in all environments right through to production. The transition to OpenShift solved our issues with code standardization across different machines. Its inbuilt DevOps features like pipelines and workflows are an added advantage. We chose OpenShift over Amazon EKS and Google Kubernetes Engine due to its hybrid nature and common functionality checks across environments.
What do you dislike about the product?
I don't like the high cost of Red Hat OpenShift compared to other alternatives in the market. The initial transition phase is complex and takes a lot of time to set up, which can be overwhelming. Also, it's heavy on processing, requiring more resources than we initially had.
What problems is the product solving and how is that benefiting you?
I use Red Hat OpenShift to deploy and manage applications in containers, enhancing scalability and compliance. It solves code standardization issues across diverse machines, and its built-in DevOps features add value. The consistent experience across cloud, on-prem, and hybrid environments is really beneficial.
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.
Versatile, Costly but Complex Cloud Solution
What do you like best about the product?
I love that Red Hat OpenShift is built on Kubernetes, which significantly enhances my ability to streamline developer workflows. This integration allows me to leverage Kubernetes' powerful orchestration tools, providing a robust infrastructure for deploying and managing containerized applications at scale. Additionally, I appreciate the granular control it offers, enabling me to fine-tune deployments according to specific needs across hybrid cloud environments. This level of control is crucial in optimizing resource allocation and ensuring efficient application management.
What do you dislike about the product?
I find Red Hat OpenShift to be a bit costly, which can be a significant consideration when managing budgets. Additionally, even though there are numerous configuration options available, the platform tends to feel quite opinionated, which can lead to a steep learning curve for users trying to fully leverage its capabilities. Moreover, the initial setup process is somewhat complex, which can be daunting when first getting started with the software.
What problems is the product solving and how is that benefiting you?
I use Red Hat OpenShift for deploying and managing containerized applications at scale across hybrid cloud environments, streamlining my developer workflow with its Kubernetes foundation and granular control.
Streamlines Deployment but Complexity and Cost Persist
What do you like best about the product?
I appreciate Red Hat OpenShift for its ability to streamline developer workflows in application development and modernization. Its unified enterprise-grade Kubernetes platform simplifies complexity, automates manual tasks, and ensures consistency across deployments. I love its consistent and automated environment which allows developers to build and deploy applications effortlessly across various platforms. The initial setup is highly automated, requiring minimal user input beyond configuration, which the cloud provider and Red Hat manage effectively. This automation simplifies the process significantly, allowing for a quick and efficient deployment through the Red Hat Hybrid Cloud Console.
What do you dislike about the product?
I find Red Hat OpenShift to be quite complex, particularly when managing configurations for security settings, networking, and storage across multiple clusters and environments. This complexity can make the initial setup challenging and often requires a significant investment in training and support. Additionally, the cost associated with using Red Hat OpenShift is a concern, given the resource demands it imposes. Furthermore, there are certain integration issues which can complicate its use with other tools or systems, affecting the overall seamlessness we aim for in our workflows.
What problems is the product solving and how is that benefiting you?
Red Hat OpenShift simplifies application development and modernization, automates manual tasks, and ensures consistency by providing a unified, enterprise-grade Kubernetes platform, streamlining developer workflows.
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.
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 Containerization and Deployment
What do you like best about the product?
I appreciate Red Hat OpenShift for its seamless support in hosting our Maximo application suite, notably through its capabilities in easy containerization and simplified deployment processes with pipelines. The platform stands out for its ease of installation and maintenance, which significantly reduces the complexity typically associated with such tasks. Moreover, I find the options like auto-scaler of nodes and descheduler extremely valuable, especially as the auto-scaler adeptly adjusts the number of nodes based on utilization, ensuring optimal load management and consistent performance. This automation is crucial in maintaining a reliable performance without manual intervention. The initial setup was straightforward, facilitated by using playbooks, which helped streamline the process efficiently.
What do you dislike about the product?
I find that the monitoring features in Red Hat OpenShift could be improved. Specifically, there is a lack of inbuilt viewing dashboards that I believe would enhance the usability and effectiveness of the monitoring capabilities.
What problems is the product solving and how is that benefiting you?
I find Red Hat OpenShift streamlines containerization and deployment, making hosting applications easy. It supports autoscaling for performance and maintains minimal load, while installation and maintenance are straightforward.
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.
Integration and automation have transformed deployment and maintenance
What is our primary use case?
In our country, our customer's main use cases for the Red Hat OpenShift Container Platform involve a journey that has begun to migrate the old legacy banking solutions towards the new containerized platform. Hence, in these cases, the Red Hat OpenShift Container Platform is a de facto standard, and there are a lot of requirements regarding that.
Currently it is mainly used in banking, and in some telcos as well, but we are not exposed to telcos right now for the OpenShift. We are mainly focused on financial sectors.
What is most valuable?
In terms of features in Red Hat OpenShift Container Platform, I find the orchestration itself quite useful for my customers because it integrates with lots of tools. For the platform plus, the security layer and automation itself are quite amazing.
Regarding how Red Hat OpenShift's policy-based governance helps to maintain application security at scale for my customers, that is also another education part we have to explain a bit. We face a struggle in explaining it to our customers as well, but the feature is quite good.
What needs improvement?
Regarding the learning curve, the customers actually do not need the technical nitty-gritty details; they need to know about the containerization journey because they are not familiar with it. They know it as a theory, but they don't understand anything about its practical implications. That's the main challenge. The solution itself doesn't require a high learning curve; it is actually quite good to manage. However, application developers and managers have to understand the beauty of it, and that is the challenge. If Red Hat can execute some programs regarding that, it will help.
Regarding Red Hat OpenShift Container Platform, it is expensive according to market feedback. Notably, the platform plus is perceived as quite expensive and some features from an infrastructure perspective are lacking.
For how long have I used the solution?
I have been working with the Red Hat OpenShift Container Platform for approximately two years from now.
What was my experience with deployment of the solution?
Regarding the auto-scaling capabilities, in most cases, the applications are not ready to handle the auto-scaling part. The reason is that the development was not done that way.
In most cases, the software has to support that auto-scaling feature, and we face that scenario quite often. In very few cases, the applications are quite ready, but in most cases, they don't support it.
What do I think about the stability of the solution?
I have no complaints regarding the stability of the platform. It is always stable.
How are customer service and support?
Not yet have I ever been in contact with Red Hat support for the Red Hat OpenShift Container Platform, but there may be some scenarios coming in the future.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We have experience with VMware solutions, as we are quite familiar with these infrastructure solutions.
We are quite familiar with VMware Tanzu, VMware ESXi, vSphere, vCenter, and vCloud Foundation as well.
How was the initial setup?
Regarding the initial setup, it is pretty easy to set up the container platform.
What was our ROI?
Regarding return on investment, my customers have not yet seen value in money while or since implementing the Container Platform. We can only comment on that one or two years later, as the customers just began to adopt it. We need to see at least one or two cycles before commenting on that.
What's my experience with pricing, setup cost, and licensing?
Regarding whether Red Hat OpenShift Container Platform is expensive or if the price is reasonable for my customers, to me, the services it provides should incur some costs, but based on market feedback, it is quite expensive. Notably, the platform plus is quite expensive according to the market. While the features it provides and the benefits it adds should have some upfront license fees—this is quite okay with me—marketing it is seen as expensive.
What other advice do I have?
If I summarize the main benefit of this solution for my customers, it is the management of both virtualized and containerized environments, where the containerization will be more focused in the future. The benefit is clearly visible. However, for the customers who are mainly virtualization focused, the benefits are not quite exposed to them, resulting in struggles with customers who focus only on virtualization as they want some alternative to VMware, VMware ESXi and similar solutions.
Through my experience, I do not actually have any suggestion for improvement for Red Hat OpenShift Container Platform because it is a platform as a service provider cloud. While we work with OpenStack as an infrastructure as a service provider system, OpenShift lacks some of its features from an infrastructure perspective. However, from an application point of view, the current features are quite good, and the flexibility of using the system is commendable. In the near future, there will be some upgrades according to market demands, but actually, nothing to blame at it.
Before planning to use the Red Hat OpenShift Container Platform, my advice is that each customer should have a try from a technical point of view, as businesses think in a different way. Before deciding, they should compare features side-by-side and should not ignore OpenShift. Once they have tried it, I think they will stick with it.
It is scalable for my customers, and it is easy to scale.
On a scale from one to ten, I rate Red Hat OpenShift Container Platform a nine.
showing 1 - 10