Red Hat OpenShift Container Platform Reviews

I am using it for my critical system, specifically for the payment system.

Especially the security side is nice. On the other hand, there is firm support in the background. This is helpful for me since I am also native to Bandit system. On OpenShift side, I can get support from Airflow. It is a good aspect. It is important for critical systems.

I have used it for approximately three or four years.

I would rate stability between seven and eight out of ten.

It is easy to expand. Scalability is rated nine out of ten.

Quality of support may be improved. I would rate it seven out of ten.

Neutral

It is not too simple, however, it is not too hard either. It was a normal installation.

I know Kubernetes, however, I am not aware of other alternatives nowadays.

It is easy to expand it. I would give it a rating of eight out of ten.

We have a monolithic application, and our primary use case is to implement microservices. We needed Kubernetes, but instead of going with plain Kubernetes, we chose OpenShift because it has a well-designed UI, more advanced features, and better security.

The product provides great visibility in the form of metrics over our systems. The infrastructure team monitors the platform with their personal tools and dashboards and can see how it deals with loads, security threats, if bugs are present, etc. Then they can send reports to the rest of us in the organization.

The solution's CodeReady Workspaces reduce project onboarding time in the region of 10-15%.  

The CodeReady Workspaces also reduce the time to market; a rival vendor released an offering we had to counter, so we used the platform to implement and deploy our counter in three to four days.   

One of the best features is monitoring; we can see metrics via visual aids when the load increases, for example.

The software is user-friendly and straightforward to use, which is favorable to a developer.

The system also takes care of itself regarding scaling; the platform can up and downscale automatically depending on demand.  

With OpenShift, there is no need to learn new technology, as the skills required for Kubernetes carry over; the commands are interchangeable. Therefore, OpenShift is a developer-friendly tool.

We use the solution on the vendor's OpenStack Platform, and in terms of the ease and speed with which it enables us to create infrastructure, it's very straightforward. We can set up an environment within a day or two, and it's a very convenient way to develop.  

The infrastructure created by the solution on the OpenStack Platform is very robust; we created communication metrics: a shield where all VMs, master, and worker nodes communicate from subnet to subnet. We designed these and gave them to Red Hat, where they developed the ISO clients for deployment from day one. After gaining hands-on experience, we could create our own and implement a cluster.   

OpenShift is highly effective at creating infrastructure that can be flexibly sized to meet specific needs on the OpenStack Platform. The minimum basic configuration is three masters, three infra, and two worker nodes. When a load starts passing through this setup, and we reach a certain threshold, say the worker machines are running at 60%, we can add another node, another VM. We have added eight to ten VMs in this way before. After experimenting with different configurations, we get a feel of which one to implement for a specific use case within the production environment. If we want to scale up, we add worker nodes; nothing else is required.  

OpenShift provides solid security throughout the stack and the software supply chain; the solution has an inbuilt image registry and doesn't allow outside images, making the system more secure. The platform also features a Compliance Operator, which assesses the compliance of API resources and the nodes running the cluster.  

I want to see more incorporation of native automation features; then, we could write a code, deploy it directly to OpenShift, and allow it to take care of the automated process. Using this method, we could write one application and have elements copied or pasted to other applications in the development process.

There are some gaps in the solution's security, so there is room for improvement in the security and compliance features. Protection against ransomware attacks would be welcome, much like in Google Apigee.

We've been using the solution for two years.

OpenShift's current stability as of 4.10 is excellent; I don't see any issues. From 4.0 to 4.6, the product wasn't stable, and in many cases, nodes went down, taking down other nodes, and we had to follow up on clusters a lot. After 4.8, the stability issues were fixed, and we haven't had a problem in a year.

The platform is highly scalable; we simply need to add VMs to accommodate the amount of traffic we have, which is a straightforward task. Eight to ten VMs is sufficient for millions of users, and we can easily implement them in a cloud-based or on-prem environment. There are around 50 total users across our Dev Teams, and the solution was able to support one million users of our applications per second without an issue. 

Overall, the customer support is good. There's a ticket process with a priority level from one to three, indicating the highest and lowest priority, respectively, with two in the middle. Level one means production is impacted, and support responds rapidly to help with a client team. There are some delays with the lower-priority tickets, but they are there when we need them most. They could have better internal communication so they are all on the same page, as we are sometimes asked the same questions by different people and have to re-explain the issue.

Neutral

We previously used Kubernetes and switched because it's more complex from the developer, management, and maintenance perspectives. It doesn't have a proper UI, so knowledge of Linux is required to operate the CLI. However, with OpenShift, a newcomer can log in and run the solution using the UI, which is an excellent capability for a development company. OpenShift isn't restrictive; anyone can use it, making it a good choice.

In addition to the UI, OpenShift has more advanced features, such as the Internal Image Registry, which can restrict malware images. The product is also straightforward to deploy and has good integrations with other tools like Jenkins.

The initial deployment was straightforward and took two days. At most, two staff members are required to deploy and maintain the solution.

The pricing and licensing are handled on an upper management level, and I'm not involved in that, but I understand the solution to be somewhat pricey.

I rate the solution an eight out of ten. 

We recently experienced a Log4j vulnerability issue, and the OpenShift team released a patch to which we upgraded, but they could have done a better job.

Regarding the platform helping us meet regulatory constraints, I have yet to deal with this area.

In terms of automation, most people I know use Github, Jenkins, or some other third-party platform and integrate with OpenShift.

We didn't consider building our own container platform because Kubernetes is an excellent platform, and OpenShift is built on top of it. We're satisfied with what we have and see no need to start from the beginning.  

Red Hat is an excellent partner; we never shared code, but we used to have review meetings where we shared room for improvement with the product and gave some suggestions. For example, we would like a backup process or system implemented, and we have communicated this to Red Hat.  

I have been using OpenShift Container Platform as a container of network functions for customer's telecom industry. 

One practical example of how OpenShift Container Platform helps us is in deploying security updates quickly, which is superior compared to other solutions like Coverness, Canonical, Kubernetes, Rancher, etc. However, there are areas for improvement in networking, architecture, and cloud aspects of the solution.

I find the security features and use of operators in OpenShift Container Platform highly valuable. The container update capabilities and OpenShift data foundation for storage are also important features.

I believe OpenShift Container Platform can improve in networking, architecture, and cloud areas by reducing deployment time, lowering costs, and streamlining engineer resources. Additionally, I would like to see more Azure I/O functions in the next release.

I have been using OpenShift Container Platform for four years.

The platform is stable and capable, covering various customer needs.

The scalability of OpenShift Container Platform is excellent. It allows for quick scale-outs with new workers, making it very efficient and is used by eighteen engineers for telecom purposes, impacting business significantly.

Technical support from OpenShift is decent but could be improved in some locations.

I find the initial setup of OpenShift Container Platform to be moderately complex. The deployment involves steps like installation, configuration, and deploying common services on-premises. Deployment typically takes around four hours and involves a team of two to four people. I'm not involved in maintenance. 

I'm not familiar with pricing or financial aspects. In terms of effort versus benefit, it's worth it.

My advice for new users is to explore the platform thoroughly as it's complex yet reliable. I would rate their customer service a seven out of ten. Overall, I rate OpenShift Container Platform a nine as it's a good product with room for improvement.

I work in a bank and we develop new microservices based on mainframe legacy systems. They want to start developing new microservices to reduce the calls to the mainframe. DevOps in Bank Hapoalim uses OpenShift as a platform and all the services are deployed automatically to avoid the problem of services being unavailable. So the main use case is to modernize the existing legacy systems. All the big projects of the bank are going through this modernization, with a new architecture and deploying stuff through microservices.

It makes our work much easier. Everything works automatically: the pods, memory, and CPU grow automatically. We had so many systems on the old technologies and it's very hard to modernize them. But this tool, OpenShift Container Platform, helps a lot. If we want to keep up with the market and be a strong organization, we have to support modernization. We can't see all the banks making changes and still go with the old systems.

Also, the department that's in charge of it, DevOps, has given us more dashboards so that we can see more details, exactly what's going on in terms of timing and everything. They give us all the details we need to see about the microservices.

It's an easy platform to use.

I'm not sure if this is an issue with OCP, but it takes time to deploy. I'm not sure because we have pipelines and Jenkins jobs that deploy the microservice so it takes time. It can take 10 to 15 minutes to deploy a microservice. The CI/CD process takes a long time, and if it's because of OCP, that is something that can be changed.

I have been using OpenShift Container Platform for about two years.

Overall it's stable. Sometimes I see problems with the stability, but I'm not sure that the problem is with OCP. There are things that we need to explore more deeply, but I would say it's stable.

It scales microservices automatically.

We have about 1,000 internal users of OCP and about a quarter of them use it daily.

We did not use any other container management software.

There were several other departments involved in the setup. 

It was done in-house.

It's a very cool product. You can trust it. We have plenty of complicated microservices systems deployed through this platform, and it does the job. We see the results. I only have good feedback about it.

It's nice to see technology getting better and better, doing things automatically. The platform can fit every organization, with the right configuration. It can do whatever you need it to do. It's very impressive to see how the technology of this platform does it.

We use the solution to manage our digital assets like containers and applications.

Integrating the product into our existing infrastructure was easy. We did not face any issues.

The price must be improved.

I have been using the solution for six years.

I rate the product’s stability a nine out of ten.

The product’s scalability is good. I rate the scalability an eight out of ten. We have around 15 users.

The support people help us whenever we require their assistance. A partner provides us with the first-level support. The support has been good, but it is not direct support. We have a problem that has not been fixed for a long time.

Positive

I rate the ease of setup a six out of ten. The project was ten months long. The deployment took a month.

I rate the pricing a four or five out of ten.

I have also used Docker and Kubernetes.

I will recommend the solution to others. Overall, I rate the tool a nine out of ten.

We use the OpenShift Container Platform to deploy applications. It helps to deploy them from a monolithic to a microservices approach. 

The tool's most valuable features include high availability, scalability, and security. Other features like advanced cluster management, advanced cluster security, and Red Hat Quay make it powerful for businesses. It also comes with features like OpenShift Virtualization. 

OpenShift Container Platform needs to work on integrations. 

I have been using the solution for two years. 

I rate the tool's stability an eight out of ten. We encountered certain bugs and issues, which were resolved once we raised them with Red Hat. 

I rate OpenShift Container Platform's scalability a ten out of ten. The autoscale feature is particularly beneficial for managing varying traffic loads on the platform. It automatically deploys additional VMs in response to high traffic and scales down when the traffic returns to normal levels. This feature is more powerful when deploying the OpenShift Container Platform on cloud platforms like AWS or Azure, where it adapts to the fluctuating traffic demands. My company has 15 customers who are mostly enterprise businesses. 

Red Hat offers good technical support. 

Positive

I rate the product's deployment an eight out of ten. It was a little complex. There are two to three types of initial configuration, including UBI. UBI is complex. Deployment takes around two hours to complete. 

The deployment process involves some complexity. We create configuration files and distribute these files to the platforms we work on, such as VMware or Nutanix. Subsequently, we initiate the initial deployment and configuration of OpenShift.

The solution is expensive, and I rate it an eight out of ten. There is a subscription called OpenShift Plus, which offers additional features and products the vendor provides to complement the OpenShift Container Platform. These include ACM, Red Hat Quay, and Red Hat OpenShift Data Foundation.

I recommend studying the documentation thoroughly and preparing the infrastructure according to the guidelines. Following the documentation is crucial, and most issues reported were related to network problems. Therefore, I suggest becoming proficient in troubleshooting network issues to identify and resolve problems. I rate the solution a nine out of ten. 

The principal use case of the platform is the transition and migration to the cloud. The second one is the modernization of our integration platforms.

The usability and the developer experience. The platform has a centralized consultant that is easy to use for our development, operations and security teams.

The price needs to be improved in OpenShift Container Platform.

When I choose this, the product is the first factor that we have to make a long analysis to compare the real cost for the other services. However, price is high.

I have been using OpenShift Container Platform for five years. We started with OpenShift Container Platform and now we have OpenShift Container Platform tools. 

I would rate the product’s stability a nine out of ten.

I would rate the tool’s scalability a nine out of ten.

The solution is difficult to set up because of the limitations of the premises. 

Overall, I would rate the product a nine out of ten.

I usually help companies design their environments, find workloads efficiencies, suggest best practices, and provide an overview of the environment, which involves consultation and a focused-oriented approach. I also deploy and develop solutions for companies. I do end-to-end deployment for companies.

OpenShift Container Platform is used by companies moving from their old monolithic environment to a microservices-oriented architecture. If a company wants to do a BAU sort of stuff, they already have OpenShift Container Platform, but they need someone to drive it or work on its day-to-day automation while looking at its integration with Ansible or Puppet.

People choose OpenShift Container Platform because it's an open-source and Red Hat Kubernetes product. Red Hat has made Kubernetes command-line oriented, obscure, and hard to learn. OpenShift is easier to learn for a newbie, especially for someone who has not used CLI. The support structure of OpenShift is pretty good and absolutely terrific. The bug fixes and patching capabilities, along with the whole ecosystem of OpenShift Container Platform, are very mature from a technical standpoint or from an enterprise standpoint. If you are a big company and invest a lot of money in certain solutions, you need and expect top-notch support and features of very high quality. OpenShift Container Platform is a very good way to get in started in this whole containerization journey for some companies because the underlying product is from Red Hat, which has its own benefits. The aforementioned factors play a role in the decision-making process of most companies.

I have only been working for two years on OpenShift Container Platform, and I have only seen good stuff so far. Hopefully, in the next two years, I will have a bit more hands-on experience to find out some pain points in the product.

There are no perfect tools. Many things can be done better in a product, but I don't know how to make it possible. Once I have done enough with the tool, I should be able to give you a bit more insight into the product's pain points.

The interface could be a bit more useful or better. The product's interface is a bit buggy.

I have been using OpenShift Container Platform for a couple of years. I am a consultant who specializes in Red Hat products. I am a Red Hat-certified engineer.

The tool is scalable enough because it is available across the clouds, like AWS or Azure. You can have the tool deployed on-premises too. I think it's a pretty scalable tool.

The solution's technical support has been pretty good. Red Hat offers the best support to its users.

I am a person who is a bit more infrastructure-focused. JBoss is a middleware software, and I don't really work in that space. I am more into the underlying infrastructure, Red Hat Enterprise Linux, Red Hat Containers and Kubernetes, and that sort of stuff, including OpenShift and OpenStack. I am not really into the application layer.

Overall, I rate the solution a seven out of ten.