We use this solution for internal and external security for a banking environment. We control the user environment and develop codes.
I'm using version 4.4. It's deployed on a private cloud. We also have physical servers.
We use this solution for internal and external security for a banking environment. We control the user environment and develop codes.
I'm using version 4.4. It's deployed on a private cloud. We also have physical servers.
It has a feature to automatically scale up or scale down. If my application is running in peak hours, it will automatically increase.
OpenShift provides us with the flexibility and efficiency of cloud native stacks, while enabling us to meet regulatory constraints.
Automation could be improved. It has a major dependency problem with IBM products. It takes too much time to upgrade one portion to the next portion. We faced a lot of issues with upgrading our DC and DR environment to version 4.10.
It should be easier to migrate our environment into the cloud to easily maintain our revenues on-premises, hybrid, and in the cloud.
I have used this solution for one year.
The server stability is fine for the OCP cluster.
We're in direct contact with OpenShift and we're an IBM partner, so we have two-way communication for any issues we face in the OCP cluster. We also have a strong internal team in our company.
I would rate technical support as nine out of ten. We're not facing any upgrading in our OCP cluster, but we're facing it in our IBM product.
Red Hat gives us excellent support as a partner.
We have to download all the images into a single point of contact. We have to load all of the images into a booster and push the images to a cluster for installation. You can directly get the images on the cloud implemented, so it's easy.
Deployment takes a week. We have had a lot of internal issues and internal firewall port communication.
For master server creation, it doesn't take more than an hour.
We're using other Red Hat products.
I would rate this solution as eight out of ten.
Most clients working on container technology want to move to the public cloud. With container technology, they can deploy Apache on Azure, AWS, GCP, or any other cloud platform.
The best part of OpenShift is you can migrate any OpenShift provider's container to any platform. If you want to migrate your containers from Azure to AWS or from on-premises to Azure, you can do so easily.
We can build a complete CI/CD pipeline on Azure using Azure tools or third-party tools. Azure Red Hat OpenShift does not include all CI/CD pipeline tools, so third-party software can be used. Red Hat builds some of the CI/CD pipelines sold on the Red Hat Platforms, which are used for any cloud platform, such as AWS, Azure, or Google Cloud Platform. Red Hat should provide this because we don't want to use third-party tools like Jenkins or other automation platforms.
I have been using Azure Red Hat OpenShift for one and a half years. We are using V4.12 of the solution.
I rate the solution’s stability a ten out of ten.
We cater this solution to high-end customers.
I rate the solution’s scalability a ten out of ten.
We have to wait sometime for the support engineer for specific issues.
Neutral
The initial setup is not easy or not difficult. Azure Red Hat OpenShift is a complex platform, but it is also very powerful. We need to use some Azure resources, such as certificates and routes, to run it effectively. This means that we have some dependencies on the Azure platform.
Deployment takes two and three hours to complete.
I rate the initial setup a six or seven out of ten, where one is difficult and ten is easy.
The product is affordable.
I rate the product’s pricing a three out of ten, where one is cheap, and ten is expensive.
Overall, I rate the solution a nine out of ten.
I had been using Azure Red Hat OpenShift for corporate integrations, trying to build and develop a digital business.
We recently put in production a new solution based on the Oracle platform. As a platform, this solution needs to integrate with legacy systems that are not appropriately adapted to the cloud-native solutions, and this is the cupping layer.
Azure Red Hat OpenShift and its integration tools provide the tools we need to integrate legacy systems with digital products in a special manner.
The solution is supported by Red Hat and Microsoft together, and we have SLAs and SLOs to guarantee our resilience and operation. The solution's support and its automation tool that ensures we are secure and appropriately configured are the most valuable features of Azure Red Hat OpenShift.
Azure Red Hat OpenShift's support should be improved. Sometimes, we have to act together with the Microsoft and Red Hat teams in some troubleshooting situations.
I would like to see something specifically developed or customized for analytics solutions in order to support data pipelines. Sometimes we have to build some predictive machine learning models and deliver them to the production environment. I don't have any DevOps automation or data ops specifically for this kind of data-intensive application.
I have been using Azure Red Hat OpenShift for three years.
I rate Azure Red Hat OpenShift a nine out of ten for stability.
I rate Azure Red Hat OpenShift an eight out of ten for scalability.
Azure Red Hat OpenShift's initial deployment depends on the problem that we have to solve for business. Sometimes we have a more sophisticated data pipeline interacting with different data sets with many transformations, and sometimes it's simple.
We have seen a return on investment with Azure Red Hat OpenShift.
Compared to other cloud environments like Amazon or Google, Azure Red Hat OpenShift is an expensive solution. I rate the solution a six out of ten for pricing.
We are currently using version 4.12 of Azure Red Hat OpenShift.
Overall, I rate Azure Red Hat OpenShift an eight out of ten.
