Red Hat OpenShift is used to host all services running on containers on specific ports for both production and non-production environments.
Red Hat OpenShift is utilized in the healthcare sector.
Red Hat OpenShift Platform Plus
Red HatExternal reviews
283 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Has supported container-based service hosting while slower support impacts resolution time
What is our primary use case?
What is most valuable?
Red Hat OpenShift provides good value as a cloud service, comparable to other public clouds such as AWS and Azure, but it functions as a private cloud rather than a public one.
A smaller cloud running on containers enables easy deployment with the ability to scale up and scale down, and it can host multiple services on the same platform.
What needs improvement?
Red Hat OpenShift is currently running with VMware, and there are some issues on the storage side that are still being addressed.
The support from Red Hat is rated around a six or seven in those kinds of cases.
Support could improve with faster response times, as responses are currently quite slow.
For how long have I used the solution?
The team has been working with Red Hat OpenShift for over five years.
How was the initial setup?
The initial setup for Red Hat OpenShift is easy to deploy.
What about the implementation team?
There are approximately two resources working on the Red Hat OpenShift cluster for deployment.
The DevOps engineer and the Red Hat OpenShift Linux engineer are the job roles required for deployment.
What's my experience with pricing, setup cost, and licensing?
There is no free open-source version available; a license must be purchased for Red Hat OpenShift.
The pricing for Red Hat OpenShift is considered quite high.
Which other solutions did I evaluate?
Red Hat OpenShift cannot be compared with other options for PaaS clouds because other private services have never been used.
There is no current knowledge of other available options.
What other advice do I have?
I am not familiar with the mobile app platform for Android.
I don't have experience with VMware or AWS products at this time, although a team member may be working on the technical side.
My focus is on the management side rather than the technical side.
Microsoft tools are not being used.
The team is focused on the Linux side for the private cloud for Red Hat OpenShift.
I have minimal familiarity with Red Hat OpenShift. I don't have experience with Red Hat OpenShift Data Foundation. The technical side of Red Hat OpenShift is handled by a team member. Management tools, help desk software, or ITSMs are not being used. The overall review rating for Red Hat OpenShift is seven out of ten.
Microservice Build and Deploy
What do you like best about the product?
ease of development and Deployment & next gen AI development
What do you dislike about the product?
RedHat OpenShift AI limited to certain models only and not supporting other products
What problems is the product solving and how is that benefiting you?
Developing Microservice level offering and Production grade performance as well as security implementation
Observer of our Openshift Red Hat engagement
What do you like best about the product?
So far it seems to be a reliable virtualization platform
What do you dislike about the product?
It's fairly complex initially, a small learning curve to navigate
What problems is the product solving and how is that benefiting you?
Container management and virtualization
A nice managed bespoke collection of best practices and tooling for K8S managed containers and vms
What do you like best about the product?
If you don't have the time, skills, or desire to set up your own kubernetes/ hypervisor infrastructure ( on top of your actual product) OpenShift can provide a mostly lock in free solution for you. You do have to drink the Kool-Aid, but you don't have time to make your own Kool-Aid, so shut up and enjoy.
What do you dislike about the product?
Part of being bespoke is they have made decisions that help more tightly bind you to other products in their ecosystem. Of course there is an cost and myriad of Licensing complexity to extract the most revenue from you. That is the trade you make for not having to do a whole bunch of work yourself.
You will still need to be able to debug and understand all the components when things go wrong, or invest in other layers of support for that. This is just the toolset. This is like "Snap On", and your still the mechanic.
You will still need to be able to debug and understand all the components when things go wrong, or invest in other layers of support for that. This is just the toolset. This is like "Snap On", and your still the mechanic.
What problems is the product solving and how is that benefiting you?
Time to start
Openshift is good, but too heavyweight
What do you like best about the product?
It is user friendly and secure. It is easy to set up
What do you dislike about the product?
Too many pods. Too much memory. A lighter version would be good to heave.
What problems is the product solving and how is that benefiting you?
Edge computing / telco
Adopting a flexible and efficient approach with noticeable improvements in operational costs and continued challenges in job management
What is our primary use case?
We already were having that microservices architecture, so there was not much change from that perspective. We had small services, so here we had to create multiple pod IDs. Even today, we are using a hybrid microservices architecture. Our DB still has two or three services that hit the same database. From that perspective, there was not much change that we did in our case.
What is most valuable?
We have certain applications on-prem on physical servers. We had some on Windows and some on Linux. There we had requirements where every time we had to manage extra load, we had to spawn a new Tomcat node. Scaling was one of the issues we were facing, and every time we had to scale up, it was a challenge. Plus, we had to procure infrastructure and do a lot of configuration and setup for the new instance being launched.
Once we set that up, scaling down was a challenge as we did not always bring that down when not needed. When we did not have too much traffic, we still had a lot of infrastructure lying idle. At the same time, when we had high load, we were not able to scale up quickly.
There was too much patching that happened, and every time we had to patch something it became a challenge. There were versioning issues with operating systems versus Java and other technologies we were using. That is why we moved to containerization, where we defined what operating system we need, what Java version we need, and what steps we want to do. Containerization helped us create that one unit we wanted to deploy. Red Hat OpenShift helped us with managing scaling up and scaling down.
Because it was centrally managed in our company, many metrics that we had to write code for were available out of the box, including utilization, CPU utilization, memory, and similar metrics. We performed multiple transformations from physical servers to Red Hat OpenShift, and some from virtual servers to Red Hat OpenShift.
The OC utility tool is something we use very often for replication, replica sets, and config maps for managing all environments and secrets. This is very useful for us. Routing is another beneficial feature we get, so we do not need to manage or do too many things for load balancing.
What needs improvement?
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The entire company uses Autosys, but we are not able to integrate it effectively.
We need intermediate servers to run OC utility commands and initiate the cron job. We have to do a lot of modifications to ensure our batches work properly. With physical or virtual servers, even in AWS, we are able to write and manage multiple jobs. Managing batches in Red Hat OpenShift has been a significant challenge.
Integrating third parties is a challenge with Red Hat OpenShift. For example, with Elasticsearch, onboarding itself was difficult, running file beats and dealing with routing issues. It is not straightforward, especially since we have some components in AWS as. AWS has many capabilities that come out of the box and are easier to work with compared to Red Hat OpenShift.
Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud.
What was my experience with deployment of the solution?
The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud. Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. For the use cases we dealt with, we have not seen much challenge with AWS. It has been better for us, but due to our requirement of being on private cloud for some applications, we are using Red Hat OpenShift.
What do I think about the stability of the solution?
We do not have any AI products at this time.
What do I think about the scalability of the solution?
We have certain applications on-prem on physical servers, some on Windows and some on Linux. We had requirements where every time we had to manage extra load, we had to spawn a new Tomcat node. Scaling was one of the issues we were facing, and every time we had to scale up, it was a challenge. We had to procure infrastructure and do extensive configuration and setup for new instance launches. Once set up, scaling down was also a challenge as we did not always reduce capacity when not needed. When we did not have much traffic, we still had substantial infrastructure sitting idle. Simultaneously, during high load periods, we were not able to scale up quickly.
How are customer service and support?
We have support available, but we never had to use it because we have our own internal teams who provide support. We have not encountered any issue where we had to reach out to Red Hat.
How would you rate customer service and support?
Neutral
How was the initial setup?
It is not difficult to onboard onto Red Hat OpenShift. Once you understand deployment configs, configs, replica sets, the basic components, routes and all, it is straightforward to onboard an application there. This applies mainly to services. Beyond that, it becomes challenging. We have not tried too many things because we struggled with batches. Getting things up and running in AWS, such as Kafka and Elasticsearch, is much easier than doing it on Red Hat OpenShift.
What was our ROI?
It is cost-effective. The only consideration is that you have to use it wisely. Use only what you need because it is not very difficult to add resources. It is always advisable to get the bare minimum that you need, and then add more when necessary. When you do not need the services, bring them down so you are not unnecessarily using compute resources. If you use it efficiently, then it is beneficial, which is applicable to any cloud platform.
What other advice do I have?
If you are dealing with services and need private cloud, go for Red Hat OpenShift. Regarding cost, if you compare to public cloud platforms, it is cheaper. If you are mostly on the services side and need private cloud, Red Hat OpenShift should be the solution. The overall rating is six out of ten, as it is not seen as a complete solution, but rather as a solution only for services. For other requirements such as integrations or batches, other cloud providers might be more suitable.
JDs Open shift Review
What do you like best about the product?
It has a lot of functionality and uses for the features we need
What do you dislike about the product?
It can be hard to install, configure and for new users to learn
What problems is the product solving and how is that benefiting you?
We are currently in progress of replacing VMware with Open shift virtualization
My expirience y very good for your products
What do you like best about the product?
Support is good and your platform is very easy
What do you dislike about the product?
Cicd is a very easy to used and support is good
What problems is the product solving and how is that benefiting you?
Suppor most fast
Ágile development
What do you like best about the product?
Easy to provision, intuitive platform and very visual
What do you dislike about the product?
Not easy to adapt to our legacy form of work
What problems is the product solving and how is that benefiting you?
It solves our way we develop and deploy our solutions
Open shift Review
What do you like best about the product?
It is a good container solution and with AI we can achieve so manyu things.
What do you dislike about the product?
Needs More markaeting for folks to be aware about.
What problems is the product solving and how is that benefiting you?
It is easy to use and good container solution.
showing 1 - 10