I mainly use Red Hat OpenShift Container Platform for big data processing applications that require a lot of memory. On-premises solutions are not efficient for this. OpenShift, with its ready-to-deploy environment using pods and the Apache Spark Operator, allows me to deploy, process, and insert data efficiently. I also use it in my DevOps workflows. Using Tekton as a plugin, we have customized tasks integrated with GitHub, which automates pipelines whenever commits happen to branches.
External reviews
External reviews are not included in the AWS star rating for the product.
Easy implementación and a game changer
Friendly
We are usina openshift With openshift virtualization on our private cloud offer sucessfull
Experience with OpenShift
Great platform !!!
Redhat Openshift Platform
Openshift is the new era of technological evolution.
I use openshift to management kubernetes container
Efficient deployment with resource optimization and multi-region stability
What is our primary use case?
How has it helped my organization?
Using OpenShift has allowed us to optimize our application deployment times significantly. It automates the pipeline for new features, from commit to deployment, which speeds up the process.
OpenShift also helps with stability through multi-cluster support in different regions, ensuring continuous service even if one region faces downtime. Additionally, the auto-scaling feature helps manage resources effectively, keeping operational costs lower compared to on-prem solutions.
What is most valuable?
One of the most valuable features of OpenShift is its efficient deployment process. It automates rolling out new features, packaging the code, conducting security scans, and deploying to OpenShift.
Additionally, the auto-scaling feature ensures resource optimization by provisioning new nodes when utilization thresholds are met. The support for parallel processing in big data applications and consistent region-wise replication for stability are also crucial.
What needs improvement?
There are several areas where OpenShift could improve. The interface has numerous UI bugs that need addressing.
Furthermore, the latest version has deprecated the deployment config, which has its own advantages compared to the deployment container.
Lastly, there is no built-in auto-scaling plugin at the OpenShift level; this needs to be addressed as it's available at the cloud provider level, like IBM Cloud.
For how long have I used the solution?
I have been working with Red Hat OpenShift Container Platform for five years, from the start of my career.
What do I think about the stability of the solution?
We have faced scalability and stability issues at times. To manage this, we utilize multi-cluster support in different regions like US South and US East. When one region is down, we deploy to another to ensure continuous service. This setup mitigates potential downtime and improves overall stability.
What do I think about the scalability of the solution?
The scalability features of OpenShift have been invaluable. We use auto-scaling plugins to configure minimum and maximum nodes and CPU utilization thresholds. This ensures that new nodes are provisioned when usage hits a specific percentage, which aids in resource management and application scaling.
How are customer service and support?
The customer support from OpenShift is poor, with responses typically coming only after a few hours. The technical support, on the other hand, is more knowledgeable and helpful, although the process takes a considerable amount of time.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I have worked with Kubernetes and Azure services for container management. Over the last year, I've also used AWS EC2. Each has its pros and cons, but I've found OpenShift's built-in features to be highly efficient for my use cases.
How was the initial setup?
The initial setup of OpenShift is not complex when using Terraform or Ansible scripts. These scripts automate the creation and setup of resources, making subsequent deployments straightforward and efficient.
What was our ROI?
Running OpenShift on the cloud as opposed to on-premises significantly reduces costs. Cloud services provide bundled features and scaling capabilities that would be expensive if set up on bare metal.
What's my experience with pricing, setup cost, and licensing?
OpenShift pricing varies by region. For example, a simple cluster with three nodes in DAL-10 might cost around $560 to $580 per month, subject to specific configurations like memory and CPU cores.
Which other solutions did I evaluate?
I have experience with Kubernetes, Azure, and AWS EC2. Kubernetes and OpenShift are favored for their container management capabilities, while Azure and AWS offer frequent updates and broader feature sets.
What other advice do I have?
Different companies might choose Amazon, Red Hat, or Microsoft based on their strategic goals. For startups or those needing robust container support, Red Hat OpenShift is highly recommended. For those needing frequent new features, AWS might be more suitable. Decision should be based on strategy and problem statement.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Enhanced security and streamlined DevOps with advanced feature integration
What is our primary use case?
Our primary use case for Red Hat OpenShift Container Platform is to enhance our Kubernetes management by leveraging the additional features and tools it provides. We use it to deploy applications, set up pipelines with Tekton, integrate secure networking, and facilitate AI and machine learning projects through MLOps.
How has it helped my organization?
Red Hat OpenShift has made the development processes more manageable and secure, particularly by providing its own DNS system, a pipeline solution called Tekton, and features like source-to-image. These enhancements simplify the complex tasks seen in plain Kubernetes, making it user-friendly and improving DevOps efficiency.
What is most valuable?
The most valuable features of OpenShift include its advanced security, integrated DNS system, built-in pipeline management with Tekton, enhanced networking routes, and dedicated platforms for DataOps and MLOps. These features make it a robust choice for handling enterprise-level tasks securely and efficiently.
What needs improvement?
Setting up OpenShift locally can be challenging, particularly because it requires RHL Linux and has specific restrictions. Additionally, the documentation for local setups is lacking. Improving these aspects would make OpenShift more accessible to the community for trial and development purposes.
For how long have I used the solution?
I have been using Red Hat OpenShift Container Platform for two years.
What do I think about the stability of the solution?
OpenShift is highly stable. Its performance is comparable to Kubernetes, with enhancements where Kubernetes lacks certain features.
What do I think about the scalability of the solution?
Scalability is customizable and straightforward. We can deploy it on any cloud service or our server center and scale it easily. Red Hat and AWS provide excellent support, making it easier to scale quickly.
How are customer service and support?
The technical support from Red Hat and AWS is reliable and friendly, aiding problem resolution effectively.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I have experience with Kubernetes, Docker, and Sravan for container management. However, OpenShift stands out for its security and feature enhancements.
How was the initial setup?
The initial setup for OpenShift on the cloud platform is straightforward and quick, taking five to ten minutes to initiate and up to one day to deploy all resources, depending on the complexity. For local setups, the process is more complicated and error-prone.
What about the implementation team?
Typically, three to four people are needed for deployment. This may include configuring nodes and setting up multi-cluster or hybrid environments to ensure scalability and ease of management.
What other advice do I have?
If your concerns are primarily security and feature enhancement, OpenShift offers substantial value. It is suitable for larger teams concerned about security and usability. Smaller teams with less stringent requirements might consider other solutions. Careful cost estimation is crucial to avoid unnecessary financial burdens.
I'd rate the solution nine out of ten.