Red Hat OpenShift Reviews

Our organization is the product and we have applications that are based on microservices. Our microservices are deployed on OpenShift.

The security features and the support from Red Hat are strong and they have helped our organization.

Integrating the gen case and the CSC pipeline has allowed us to automate processes in OpenShift, reducing the time taken significantly. The system runs smoothly without any issues.

The most valuable feature is the auto scalers for all microservices. The feature allows us to place request limits and it is much cheaper than AWS.

The metrics in OpenShift can use improvement. There are vast metrics and if OpenShift can provide the geometric thread that would be helpful.

I have been using the solution for two years.

The solution is stable with no downtime.

The solution is very scalable.

Generally, our tickets are resolved within 15 days.

Neutral

Based on feedback from my colleagues, the initial setup is complex with a lot of dependencies to set up the environment.

The implementation was completed in-house.

We use the license-free version of Red Hat Openshift but we pay for the support. The support fee is expensive.

I give the solution a nine out of ten.

We currently have 100 people using the solution made up of architects, developers, DevOps teams, and testing engineers.

Maintenance is required every two months to restart the ports that get hung up. The solution requires between two and five people for maintenance.

We have built our own container platform. We have lots of products deployed on OpenShift. And there are lots of namespaces all deployed on the same OpenShift control platform. Everything is running fine.

OpenShift is a very stable solution with a lot of support features. I recommend the solution.

Our use cases for OpenShift are for payments and internal bank transactions.

What I like best about OpenShift is that it can reduce some of the costs of having multiple applications because you can just move them into small container applications. For example, applications don't need to run for twenty days, only to be used up by Monday. Through OpenShift, you can move some of the small applications into any cloud.

I also find the design of OpenShift good.

My team has found some bugs in OpenShift due to continuous integration, and this is an area for improvement in the platform. RedHat should fix the bugs.

Another area for improvement in OpenShift is that upgrading clusters can be challenging, resulting in downtime.

Application support also needs improvement in OpenShift because the platform doesn't support all applications in the cloud.

I'd like upgraded storage in the next release of OpenShift, especially when I need to do a DR exercise. It would also be good if the platform allows mirroring with another cluster, or more portability in terms of moving applications to another cluster.

We're using OpenShift for the last two years.

OpenShift is a good solution, stability-wise.

The performance of OpenShift is good, but sometimes, it can be bad, depending on the network, but that's okay. That's normal. You won't have a very bad experience with OpenShift, performance-wise. You'll experience some issues from it, but it's still a good platform.

As OpenShift is on-premise, there's not much scalability from it. My team is still coming up with new clusters, and some clusters have been deployed as well, but my company isn't ready to scale OpenShift at the moment.

My team contacts OpenShift support whenever there's an issue, and it was a very bad experience. The response time needs improvement, and support didn't give straightforward answers.

On a scale of one to five, my rating for OpenShift support is a two.

The setup for OpenShift was complex, and it can only be done by a consultant. My team can do an on-premise setup and automation, but a consultant has to certify the cluster, otherwise, you can't get support from RedHat.

Deployment for OpenShift can be completed within six to seven hours depending on the infrastructure. Otherwise, it could take more than one day.

My rating for the initial setup of OpenShift is three out of five. RedHat will check the setup or configuration, and if the customer is ready to take over the process, then it's good, but what's usually happening is that the vendor isn't providing detailed guidelines, so my rating is more on the neutral side.

We used a RedHat consultant for the deployment of OpenShift.

The licensing cost for OpenShift is expensive when compared to other products. RedHat also charges you additional costs apart from the standard licensing fees.

We're currently evaluating a product from IBM.

My company uses OpenShift currently, but it's still under RFP.

OpenShift is deployed on-premises on a disconnected cluster for a financial institution.

Some maintenance is required for OpenShift. Whenever there's a bug, my team does the maintenance, but there's still a need to check with RedHat support on how to fix the bug. My team can't do the maintenance without support from RedHat developers.

Less than ten people use OpenShift within the company.

I would recommend OpenShift to others because it's a good tool for the financial sector versus public clouds such as AWS and Azure. I'd also advice others that if it's a public cloud, it's easy to manage, but if it's on-premise, then it can't be managed.

My rating for OpenShift is seven out of ten.

My company is a customer of OpenShift.

These are for some of our applications where we wanted high resiliency. In the traditional VM environment, what used to happen is that everything was dependent on the infrastructure. We wanted to move away from that particular concept. Once an application becomes stateless, it should not be dependent upon platform-related things. We wanted it to be more robust and perform at a much better efficiency. We also wanted higher availability.

We are getting everything from OpenShift at this point in time. What we're doing here is pretty much basic. Any of Kubernetes could have done it because all we're looking for is being able to manage the complete cluster.

Its interface is good. The other part is the seamless integration with the stack that I have. Because my stack is mostly of Red Hat, which is running on top of VMware virtualization, I have had no issues with integrating both of these and trying to install them. We had a seamless integration with the other non-Red Hat products as well.

One of the features that I've observed in Tanzu Mission Control is that I can manage multiple Kubernetes environments. For instance, one of my lines of business is using OpenShift OKD; another one wants to use Google Anthos, and somebody else wants to use VMware Tanzu. If I have to manage all these, Tanzu Mission Control is giving me the opportunity to completely manage all of my Kubernetes clusters, whereas, with OpenShift, I can only manage a particular area. I can't manage other Kubernetes clusters. I would like to have the option to manage all Kubernetes clusters with OpenShift.

I would like to have self-service capability. A lot of developers want to become independent today, and they don't want to depend on the Infra teams for managing, provisioning, etc. If we can give a self-service capability, in terms of building a particular Kubernetes cluster end-to-end, to developers, that would be a plus. That's the ask of the hour.

I have been using this solution for the past one and a half years.

It is a perfectly stable product. If an application is ready to be containerized, it is seamless. You will not have any hiccups.

Scaling up and down is happening, but my concern is that if we hit any kind of bugs, the open-source community won't be that active in terms of doing the bug fixes. If I get any bug, there might be a delay in getting the bug release or the patch coming up. When I'm hosting an enterprise data application on an open-source product, I will have a little higher risk of non-availability, and that might lead to revenue impact as well. Keeping that in mind, I would like to go for the enterprise edition, at least for my high revenue-generating applications.

In terms of the number of people working with this solution, I have about eight administrators. I have eight people in my team who manage the complete Kubernetes cluster for me, which is a combination of OKD and Tanzu. It is being used on a daily basis.

We are using the open-source version, and their community support is good. I don't expect a rapid response from the community, but if I post today, I usually get a response in a few hours. 

We have an enterprise agreement with Red Hat for the other products that we are using. Their response is very prompt.

We also use Tanzu, which has more limitations. If I have to use an F5 load balancer or other third-party products, Tanzu shrinks a little bit. It is not as mature as Red Hat OpenShift, which is more open to other products. I have an F5 load balancer, and I struggle a bit to integrate the F5 load balancer with Tanzu, whereas with OpenShift, it happens directly. For Tanzu, I have to have another layer on my load balancer, which is Avi. I have to use their services. Adding one more product into the environment brings some complexity, whereas OpenShift is very agile in nature. It adapts to all kinds of products that are not part of the same stack. So, I had no issues with that. I would rate OpenShift higher than Tanzu because OpenShift is a much more mature product.

It was straightforward. I had a perfect team with prior experience in OpenShift. They were able to do it without any hiccups. The community of OpenShift is very good. There are a lot of exchanges happening in the community space, which helped us in doing it in a seamless way. I would rate it a 5 out of 5 in terms of the ease of the setup.

We are currently using the open version, OKD. We plan to get the enterprise version in the future.

It is an excellent product. There are a lot of items that will be good to have in there, but based on the comparison with others and based on the kind of use cases I have seen, I would rate it a 10 out of 10.

Compared to OpenStack, OpenShift is the best product in the market. There are plenty of cloud service providers who use OpenStack or other open-source products, but OpenShift is the best. Even AWS is just an okay product, but they have different proprietary software, which is not the same as OpenShift.

The most valuable features of the solution stem from the product's GUI, and other such areas of the product have been set up. Compared to AWS, OpenShift is better.

Latency and performance are two areas of concern in OpenShift where improvements are required.

OpenShift's scalability has scope for improvement.

OpenShift's technical support team needs to improve the support they provide to my company since the support we currently receive depends on the support package we have from the ones that OpenShift offers, like platinum, gold, or silver. OpenShift's technical support team is good, but it takes time for them to find the root cause of a particular issue. One of the clients of my company doesn't face many issues with the product, so we don't use much of the technical support. I can say that OpenShift's technical support team is okay in general.

I have experience with the product, but I don't possess a large amount of technical knowledge to comment on what functionalities need to be added to the product.

I have been using OpenShift for two years. My company is a user of Red Hat products.

It is a scalable or expandable solution. Scalability-wise, I rate the solution an eight out of ten.

Eight members of my company's team use OpenShift.

For one of my company's clients, we have to deal with the technical support team of OpenShift. With Red Hat, my company has platinum support. I rate the technical support an eight out of ten.

Positive

AWS and DigitalOcean are products with which I have some experience.

Kubernetes on AWS is a bit complex to set up, whereas OpenShift is easier for me to set up. However, they use the same things during the setup process. OpenShift is just a better product for a new user compared to AWS since the former is easier to understand.

The product's initial setup is very easy, especially compared to AWS.

The solution is deployed on a public cloud since half of the deployment is in the data center and half of it is in the cloud.

My company makes payments towards the licensing costs attached to OpenShift.

During the evaluation phase, I looked at Google Cloud.

I carried out OpenShift's integration process for two or three firms as a part of the team, so it was not done by myself alone. I did carry out the integration process for AWS. Comparing OpenShift with AWS, I found the former to be much easier.

I rate the overall product an eight out of ten.

I have not used it on IBM Cloud. It is basically used on AWS and Azure. I am using a standard OpenShift.

OpenShift is a container orchestration tool. We have been using it for hosting products on container-based applications.

Actually, what happens is that the solution gives or provides that kind of stability and much more. It gives a good production environment that is much more stable and error-free. That's how the solution contributes to the productivity of my whole organization.

If we compare OpenShift and Kubernetes Harbor, OpenShift is derived from Kubernetes. However, some of the most prominent features of OpenShift are its security services and some of the policies, especially security policies that are some of the add-ons and the best things I like in OpenShift.

Some things need to be improved in the solution. Some of the storage services and integrations with third-party tools should be made possible.

I think some more things will come in, like the projects of CNCFs. I think that verified CNCF projects will be integrated into OpenShift.

I have been using OpenShift for eighteen months.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

I think the support is fine. It depends upon some of the SLAs and how things or how the SLAs have been maintained. Overall, it is fine, so I will rate the support a seven out of ten.

Neutral

Initially, the setup seemed to be complex, but the recommendations from Red Hat, and especially on the CoreOS systems, for quality, stability, and security purposes, it seems to be complex. However, once we get hands-on experience, it is very, very useful and easily maintainable as well.

I have seen a return on investment, and it depends upon the types and the nature of some of the most critical applications that have been hosted on the OpenShift infrastructure. Considering in terms of stability, performance-wise, and security-wise, if everything goes fine, I think its return on investment is justified.

The price depends on the type and the nature of the organizations, along with the types of projects that are of considerable range. I don't think the price is very much of an issue for any organization against the services being delivered over the cloud and the services of OpenSuite.

If any organization is just working on open-source technologies and wants to have enterprise support and enterprise-grade solutions, then we must go with OpenShift.

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

We use the solution for container orchestration and management. 

We have found the cluster management function to be very good with this product. Also, each new version of the product has made upgrading easier and faster to carry out.

We experienced issues around desktop security, which stopped us from implementing a new feature that had been developed. This needs to be improved in order to expand the usage of the product.

We have been working with this solution for around two and a half years.

We have found the solution to be very stable.

We have found the solution to be very scalable during our time using it, and we now have a large number of transactions passing through the product.

The technical support is good, but they have been slow to respond in the past. The issues were resolved effectively, but it took some time for this to happen.

Positive

The initial setup of the solution was hard, and took around three months to deploy completely.

We used a third-party vendor for our implementation, and they were very knowledgeable.

Depending on the extent of the product use, licenses are available for a range of time periods, and are renewable at the end of the period.

I would recommend that organizations pay a lot of attention to the initial design and setup of the solution to ensure that it is optimized for their needs, as it isn't easy to make changes once this is complete.

I would rate this solution an eight out of ten.

We are using OpenShift as a microservice platform.

The most valuable feature of OpenShift is the containers.

OpenShift can improve monitoring. Sometimes there are issues. Additionally, the solution could benefit from protective tools if something was to happen in our network.

In a new release of OpenShift, they should add Kibana, Grafana, and Elasticsearch.

I have been using OpenShift for approximately two years.

OpenShift is stable. However, I feel it could be better but the local implementor is not giving us all the information.

We use OpenShift on a daily basis. We have one engineer for the operation and a pre-engineer for monitoring. Additionally, we have more than five to handle the daily work.

We are using a local vendor for the support. They can handle level one and two support when we have issues.

The initial setup of OpenShift is complex. We have two types we do, but active active does not work, only active passive does.

We used a local vendor to do the implementation and maintenance.

I rate OpenShift an eight out of ten.

OpenShift as a solution is quite broad depending on the industry you are applying it to. For example, telco companies use the entire breadth of applications that the client wants from the web to their middle tier up to the back end. 

OpenShift is a platform for ensuring that your apps are running reliably. 

OpenShift has 100% compatibility with Kubernetes. I find using kubectl, and kubectl commands to be valuable.

The security features of OpenShift are strong when in use of role-based access. The solution is easily compatible with other solutions and the features are easily installed.

OpenShift could be improved if it were more accessible for smaller budgets. I currently mostly use Raspberry Pi, which will be over to use Kubernetes. As a platform, I am using Raspberry Pi rather than using a very large configuration computer. 

The solution requires eight or more cores of CPUs, multiplied over the number of nodes needed to make OpenShift reliable, making it susceptible to failures.

In the future, I would like to see a roadmap to have Wasm supported. If you have WebAssembly as an alternative to Docker, it would be great.

I have been learning how to use OpenShift for years, but actively using it for six months.

The solution is stable. We haven't experienced downtime. 

OpenShift is easy to scale. You just need to make sure you have the capacity to purchase and the number of nodes needed. Scalability only depends on your budget.

Currently, they are more than 10 users of OpenShift in the organization.

Technical support has been efficient, supportive, and communicative. They do not drop the ball. I would rate the customer service and support of OpenShift a five out of five. 

Positive

Previously, I had experience with VMware's Kubernetes version. VMware was very difficult to install. I could not understand the route they were taking and why there were so many steps. 

The initial setup of OpenShift is straightforward if you are an experienced platform engineer. Installing on AWS or Azure could be more complex. The product has a Terraform command to install everything.

If all of the tools that are needed and all the hardware is there, the implementation should be straightforward. I would rate the initial setup a four out of five overall.

Pricing of OpenShift depends on the number of nodes and who is hosting it. OpenShift is more expensive than other solutions, however, I think it is worth it.

Anyone looking to implement OpenShift in their organization should start with the most minimal setup for configuration. There is an OpenShift version with just the single master with a built-in worker. You will only need a single CPU and you can start with at least three masters and a single worker and scale from there as the need arises, whether it is to add additional worker nodes or as your app grows.

There is no product that compares to OpenShift. I would rate it a 10 out of 10 overall.