I use the solution for deployments with Java applications in the environment.
Red Hat OpenShift Kubernetes Engine
Red Hat LimitedExternal reviews
External reviews are not included in the AWS star rating for the product.
Unleashing the Power of Scalable Container Orchestration
Scalability and Resource Management: OpenShift enables organizations to scale their applications efficiently by providing automated scaling capabilities. It allows applications to dynamically adjust their resource usage based on demand, ensuring optimal utilization of resources and efficient allocation of compute, storage, and networking resources.
Application Lifecycle Management: OpenShift streamlines the deployment and management of applications throughout their lifecycle. It offers a range of deployment strategies, rollback options, and integration with continuous integration and continuous delivery (CI/CD) pipelines. This simplifies the process of updating applications, reducing downtime and enhancing the overall agility of the development and deployment process.
Great tool for containerization
Abstraction on the top of native kubernetes
Efficient Container Management Platform
Red Hat OpenShift Kubernetes Engine review
Red hat Open shift Kubernetes engine
Has good stability and integrates with multiple applications
What is our primary use case?
How has it helped my organization?
The solution has helped us in faster deployments of the applications.
What is most valuable?
The solution's most valuable feature is its ability to integrate with multiple applications, including inference tutor and container platforms. It helps us enhance the deployment process and make it faster.
What needs improvement?
The solution encounters lengthier downtime issues for virtual upgrades. In this case, we have to opt for alternative upgrade strategies. This area needs improvement. Also, they should release its serverless version.
For how long have I used the solution?
I have been using the solution since 2018.
What do I think about the stability of the solution?
The solution is very stable.
What do I think about the scalability of the solution?
The solution is easy to scale. Our organization plans to increase its usage for the next five years.
How are customer service and support?
The solution's technical support is excellent.
How was the initial setup?
The solution is easy to configure and run.
What was our ROI?
The solution generates a return on investment.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive but cost-effective.
What other advice do I have?
The solution is an excellent platform with a fast return on investment. I rate it a ten out of ten.
A stable and scalable solution for microservices and Kubernetes distribution
What is our primary use case?
We use the solution to split monolithic into microservices. I mostly use OpenShift as a Kubernetes distribution.
What is most valuable?
I am impressed with the product's security features.
What needs improvement?
The tool lacks some features to make it compliant with Kubernetes.
For how long have I used the solution?
I am working with the solution for four years.
What do I think about the stability of the solution?
The tool is stable.
What do I think about the scalability of the solution?
The cloud version is scalable. The solution's on-prem scalability can be improved.
How are customer service and support?
The tool's support should be improved.
How was the initial setup?
The tool's deployment takes a matter of hours to complete. You need a team of three to four to maintain the solution.
What's my experience with pricing, setup cost, and licensing?
The product's support is expensive. I would rate the tool's pricing an eight out of ten.
What other advice do I have?
I would rate the solution an eight out of ten. The tool requires knowledgeable people to manage it.
Fast development, improved quality, and easy management
What is our primary use case?
We use it for container management. It's our container management platform for our financial systems.
How has it helped my organization?
It provides flexibility and efficiency. It helps us to design and deliver applications efficiently. We can modify our application in a smaller scope. We don't need to change the whole application.
It makes development fast because we can separate applications into different parts. We can deliver applications in different phases.
It has helped to improve the quality of our end products. It has reduced the project onboarding time by 20% to 25%.
What is most valuable?
I like OCP, and the management UI is better than the open-source ones.
The integration with 3scale is very good. We use that too.
What needs improvement?
The monitoring part could be better to monitor the performance. The automation part could also be better because we had a hard time integrating our application with OCP.
For how long have I used the solution?
I've been using this solution for about two years.
What do I think about the stability of the solution?
It's stable.
What do I think about the scalability of the solution?
It's scalable for one cluster. When it comes to multiple clusters, it could be better.
We have about 100 users who use this solution.
How are customer service and support?
Their enterprise support is okay, but sometimes, their response is slow. Their response is also not accurate sometimes. It's not right.
Which solution did I use previously and why did I switch?
I didn't use it, but my company used the PKS solution.
How was the initial setup?
It's straightforward. The setup took two to three days.
What other advice do I have?
Red Hat is quite okay as a partner for helping us create the platform that we need. They do help you. They also provide training.
We use Red Hat AMQ streams and 3scale, and its integration with other Red Hat solutions is okay. The advantage of using multiple products from the same vendor is that you can get help from one company. You don't have to go to multiple companies.
It gives me the security that I need, but I didn't evaluate the security much. There is another department that's responsible for that.
I would recommend this solution to others, and overall, I would rate it an eight out of ten.
OperatorHub provides certified applications, helping us reduce time to market
What is our primary use case?
NetApp is our storage provider and we have a product called Astra Control Center. We can back up and restore our containerized applications that are running on OpenShift. We use it to create a disaster recovery site for our business-critical containerized application.
Our second use case is for cloud bursting. When we have fewer resources available on-prem, we can move some of our non-critical applications to the cloud.
Our production environment can be run on AWS or any other cloud where we've deployed OpenShift, while we have our test and development environments on-prem. Once an application is certified, it can be moved from development to the production environment using Astra Control Center.
How has it helped my organization?
The CodeReady Workspaces reduce project onboarding time. With my experience, I was able to deploy the OpenShift cluster to make development ready in one day, with all kinds of related post-installation configurations.
And CodeReady Workspaces also reduce time to market. Red Hat OpenShift provides its OperatorHub from which you can find all the certified applications that are readily available on the portal itself. It gives you a cloud catalog-type feature directly on the OpenShift console. Through that, you get a GDP that is already certified, while deploying any kind of application. That means they are made to run with your OpenShift environment. You don't need to do any research to make it work with OpenShift.
OpenShift also provides us with the flexibility of cloud-native stacks while still making it possible to meet regulatory constraints.
What is most valuable?
The most valuable feature of OpenShift is the security context constraint (SCC). The solution’s security throughout the stack is good. And security context constraints provide port-level security. It's a granular level of control, where you can give privileges to certain users to work on certain applications. That's a great security feature.
The solution also provides a lot of security features on top of a regular Kubernetes cluster, which you can control. For example, in the namespace of OpenShift, there are different kinds of access levels. If you have a development team, you can provide limited access so that a developer can only deploy your application. If you're running any business-critical app, you can restrict the users' access to that app.
Also, Red Hat provides advanced multi-cluster management. You can manage multiple clouds with one solution, and I'm happy with that.
What needs improvement?
For how long have I used the solution?
I have been using OpenShift for more than two years.
What do I think about the stability of the solution?
I have found some minor issues related to pod networking in which some of the OpenShift pods were not performing well. To resolve that, I needed to do a reinstallation of the cluster. Apart from that, OpenShift is pretty stable.
What do I think about the scalability of the solution?
The scalability of OpenShift is good, but a competitor like VMware Tanzu can run more pods on the same system or the same hardware. So there's a little room for Red Hat to make it more scalable.
For us, OpenShift is an enterprise-level platform. We have about 10,000 users and we have plans to increase our usage.
How are customer service and support?
The best part is the support from Red Hat. If you face any issues you can get great support.
As a partner, Red Hat is a nine out of 10 for helping us create the platform we need.
How was the initial setup?
The installation is very good. There are a lot of options with which you can deploy OpenShift and you can deploy it on different environments. You can directly deploy it on a bare metal server, or if you already have a VMware-based infrastructure, you can deploy it there. That automation is very flexible.
The initial setup is straightforward, but for a first-time user, it might be a bit challenging because there are certain prerequisites that you need to follow. But if you follow the installation guide and you're able to do all the prerequisites, it's very straightforward. It takes less than an hour.
I used the Assisted Installer and did the IPI installation for OpenShift. I had all the infrastructure ready and deployed one cluster on bare metal. Then I deployed the OpenShift cluster on AWS.
For deployment and maintenance of OpenShift, a team of 10 should be fine. They can handle the installation and the post-installation operations for your day-to-day tasks.
What about the implementation team?
I did it on my own.
Which other solutions did I evaluate?
I have tested VMware Tanzu but we didn't go with it because it comes in different flavors. If you want to use VMware Tanzu, for certain things, you need to buy another VMware product. For example, if you want to have pod services for your environment, you need to buy NSX. That's an extra overhead because you need a separate team that can manage NSX for you.
What other advice do I have?
You need to follow the prerequisites for the environment and then proceed with the installation. There are different ways to do the deployment but you should do it the way that is most comfortable for you.
You can also deploy OpenShift using Ansible. If you want to automate the entire process of your OpenShift installation, including the server, network, and storage, you can opt for Ansible. That way, you will have end-to-end automation for your entire stack as well as OpenShift. That is good flexibility.
The biggest lesson I have learned from using OpenShift is that you can go with bare metal and you don't need to pay extra for the VMware Hypervisor. In terms of installation or manageability, it's simple. You just need to follow some guidelines and you will be good.