Red Hat OpenShift Container Platform Reviews

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.

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.

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.

Our primary use case is to deploy Java and Angler UI codes into the platform's containers. We will soon migrate our product infrastructure to OpenShift. 

The most significant improvement has been in the microservices area, as the solution simplifies the deployment of microservices. We don't have to spend much time on the infrastructure and CI/CD pipeline, so OpenShift saves us a lot of time.

OpenShift eliminates distractions, allowing our teams to focus on innovation, features, and functionality. For example, the elementary deployment and the platform makes dealing with infrastructure very straightforward, allowing us to focus on other tasks. OpenShift taking care of infrastructure-related issues, in particular, takes a weight off us, and it feels good to focus on innovation, discovery, etc.   

The solution's CodeReady Workspaces reduce project onboarding time, and Red Hat can create a Workspace for us within two weeks. We place a request, and they start working on it; it's pretty fast because we're migrating most of the bank's processes over to OpenShift.  

The CodeReady Workspaces reduce our time to market by around 20%.   

The product is stable, reliable, and easy to use, from a well-known company, has a large volume handling capacity, and more and more organizations are moving to OpenShift.

The scale-up and scale-down functions of the product's UI are excellent.

The deployment is elementary and seamless.

We use the product on the vendor's OpenStack Platform, and in terms of speed and ease with which it enables us to create infrastructure on the OpenStack Platform, it's the best and most straightforward approach. OpenShift is excellent compared to other vendors like Google Kubernetes Engine and Azure Kubernetes Service; it's easier to use, more reliable and handles volume better. 

The solution is very good at creating infrastructure that can be flexibly sized to meet specific needs on the OpenStack Platform; there are options to increase and reduce the size to meet volume demands. 

The tool's security throughout the stack and the software supply chain is excellent; we are a large bank, so security is a top priority.  

OpenShift's security features are highly capable of running business-critical applications. The solution is exciting, and I'm looking forward to getting more hands-on experience. 

The solution's automated processes are excellent, and OpenShift has good integration potential with GitHub and Tangible, allowing a lot of code deployment automation. Plugins are also available for other CI/CD pipeline tools like Jenkins Pipeline, reducing our development time.  

The UI could be more user-friendly to drive tasks more effectively through the interface.

We used the trial version of the solution for one to two months to get hands-on experience in preparation for IBM Industry 4.0. 

OpenShift is a stable product.

The scalability is excellent; it allows for a very high transaction volume. 

OpenShift's technical support is outstanding, and I rate them highly.

Positive

I previously used Google Kubernetes Engine, and many of the bank's teams started switching to the OpenShift Container Platform. Once I got my hands on the product, I saw it was very good. The general trend in our organization is one of migrating to OCP.

I wasn't involved in the initial setup of the product, but it took around 30 minutes and I know it to be elementary. 

I'm an architect, so I have no involvement in the pricing and licensing of the platform.

We evaluated GKE and found OCP much more lightweight and easier to use. I tried with GKE but was never successful with it. However, with no background in OCP, I watched some YouTube tutorials and successfully deployed a sample project. This ease of use is essential for us, as we don't need to spend time dealing with infrastructure and can focus on the development and functional aspects.

I rate the solution a ten out of ten. 

We didn't consider building our own container platform because it's too big a job. We're a bank, and most banks focus more on developing functionality than building a container platform and instead look for the best available tool.

We also use Red Hat Linux and chose it because it's very stable and reliable.  

The biggest lesson I've learned from using the solution is how easy and simple it is to deploy, how little we need to focus on infrastructure, and how it allows us to prioritize functionality.  

Our client deployed OpenShift on a bare-metal server, and they use it to offer their customers a platform-as-a-service solution with metered billing. It's pay-as-you-go. We are currently developing our own platform. For the most part, we have enough developers, but we'll go to Red Hat when we need support.

OpenShift is an improvement over legacy monolithic applications. With OpenShift, our clients can see the new features quickly, and developers can get any software they need from the Red Hat Marketplace. It has improved our product development and the existing workload on business material applications running on OpenShift. It has improved the performance of our company's IT department. 

OpenShift complies with the security center, where the CS image is hardened by default. OpenShift is very secure. When there are updates, OpenShift will update all the patches necessary throughout the entire cluster platform. It takes care of that easily, reducing many administrative tasks. Using this product improves our compliance code significantly.

The pipelines in OpenShift are handy for developers to build and automate things quickly. It's easy to bring things online. Options are helpful for the customized solutions we can do with this product. Overall, the automations are well aligned with OpenShift. That's what I see.

OpenShift's code-ready workspaces reduce project onboarding time by about 70-plus days while reducing time-to-market by around 50 percent. 

The operating system has a live update and is more secure than any other. It's made for Atomic OS, a lightweight OS new to the market. I also like the source-to-image capabilities. The customer can directly deploy their applications from the repository. It's a highly flexible and easy way to deploy into production. 

It's a simplified network for exposing their application to the outside world. Red Hat has good built-in oversight, where it monitors the cluster performance and records everything built inside the cluster besides OpenShift. Of course, Red Hat is a pioneer in this kind of auditing. 

Telecom clients can use OpenStack as their private cloud to access secure resources on demand. When they deploy to OpenShift, it's easier for them to have a cloud-like field on their own data center. OpenShift and OpenStack are integrated. It's an ideal combination. The infrastructure created in OpenStack is a robust private cloud solution. If the developer wants to consume resources within their organization per the utilization, OpenStack is the right platform for building their private cloud.

In terms of innovation, features, and functionality, a public cloud has much more than OpenStack by itself. I prefer OpenShift on AWS or Azure Cloud. That has made it easier for the customers to benefit because they don't need to worry about their managed solutions anymore. It's the customer's choice to manage services through OpenShift or on-prem. OpenShift can be run on all platforms, including VMware, public, private, etc. It's a great solution from a consumer choice perspective. 

The codes are customized and fixed only for their own environment, so it's more secure, but we cannot assure the client's security. However, the code is validated, and Red Hat support will address any vulnerabilities or security issues that arise.

The support costs are too high. 

I've used OpenShift for the last two years.

OpenShift is a highly stable product if you're using it as a managed service. 

OpenShift is scalable. 

I rate Red Hat support nine out of 10. 

Positive

Setting up OpenShift is fairly straightforward. It takes about a week to plan and another to deploy, so two weeks max. 

They can reduce prices because Kubernetes is open-source and freely available to customers. The license cost is for deploying on-prem, so it's costly to go to a client's location to deploy things compared to open source. If they reduce the cost, more customers will choose OpenShift.

I rate OpenShift Container Platform 10 out of 10. This is a great product. Red Hat has been in the field for more than 25 years. Each product they release is more innovative and cutting-edge. 

I am the platform engineer, and the platform serves a function for end users by allowing them to deploy their apps based on their application use cases.

The most valuable feature of this solution is its scalability on demand, which allows for potentially lower costs, and Built-in resiliency. Those are the three most important ones that spring to mind.

In my experience, the issues are not always simply technical. They do stem from technical challenges, but they struggle with the topic of adoption. When you encounter all of the customer pull, there are normally several tiers of your client pop that can adopt either the fundamental features or a little more advanced ones.

The majority of the time, the challenge is determining how to drive adoption, how to sell the product to the customer, and how much time they can spend to really utilize those advanced features. If we get into much more detail, but this is from my perspective as the platform engineer and not the end customer, the ability of the end user to be able to debug potential issues with their application That is arguably the most important, let's say, work throughput in my area.

I have been working with the OpenShift Container Platform for two months.

We use version 4.9, and our legacy version is 3.9.

OpenShift Container Platform is quite stable.

OpenShift Container Platform is highly scalable.

I have more data regarding the number of net spaces and the number of apps that are tied to it, rather than how many individuals are on the receiving end of such applications which would be considerably more difficult. I would say more than three persons for each application, which is definitely driving the number near 500. This would be an approximate number.

I would rate the technical support a 10 or 11 because, in my personal experience, they are always going above and beyond to deliver the solution.

They are very caring about their customers.

Because the platform I'm working with was inherited, I wouldn't know how that procedure works here. I have, however, performed a few deployments in a considerably smaller context. 

You have at least three distinct techniques to perform that deployment using OpenShift, as well as a few of IPIs and UPIs. 

When I approached that scenario, I was thinking in terms of UPI, which stands for user-provided infrastructure in a non-homogenous, domestic cloud environment, a tiny simulated cloud environment. 

It wasn't simple, and it took a few tries to get a functional cluster structure with various control planes and many worker nodes. 

It's a difficult response to a hard subject, in my opinion, but, it is not an extremely simple or out-of-the-box solution.

The deployment took about two hours if we count the successful attempt once I had my preexisting issue sorted out. 

The upgrade would depend on the scale of the cluster. It can take a couple of minutes per node, so it would depend on the number of nodes.

In terms of the cluster that has workloads that are on production, you need to make sure that the workloads are not experiencing any issues.

I have a vague understanding of it but keep in mind that enterprise pricing differs from, I don't know, people or smaller businesses approaching them.

It largely depends on how much money they earn from the application being deployed; you don't normally deploy an app just for the purpose of having it. 

You must constantly look into your revenue and how much you spend every container, minute, or hour of how much it is working.

I wouldn't have access to that information within my company, therefore I'd assume it's in plus.

As far as I understand the situation, while this solution was inherited, the outstanding technical support is one of the main reasons it was chosen over other solutions.

I would definitely recommend having the vanilla experience because, contrary to popular belief, OpenShift is not Kubernetes; it's actually written on top of Kubernetes and adds an extra value of authentication, auditing, and logging on top of that, but it does require a familiarity with Kubernetes to properly utilize its capabilities. 

After being acquainted with Kubernetes, I believe it is worthwhile to dip their fingers and brains into the distinctions that OpenShift provides in contrast to other basic Kubernetes implementations.

I would rate OpenShift Container Platform a seven out of ten.

It is really expensive. That is not something you would employ unless you had a strong business case for your application. That is, not in terms of the enterprise version.

You may use our OKD, which is a community version we provide, which is less expensive. However, it is not a supported version of OpenShift; it is only supported within the community. However, because the OKD community is small, there is a low likelihood that someone would respond to your inquiry if you run into problems and need to locate answers elsewhere.