Red Hat OpenShift Service on AWS

My main use case for Red Hat OpenShift is training for several products, mainly for container orchestration, and I am currently using OCP. Previously, I trained on different products such as virtualization and Red Hat Enterprise Linux, and I also work with new products such as Red Hat AI OpenShift, which are useful for cluster management at the enterprise level.

When I am using Red Hat OpenShift for training and cluster management, I typically run different kinds of applications that are deployed on containers. People from both the development team and the operations team are involved; the development team focuses on automation and deliverable items, while the operations team mainly manages the administration work, including managing workloads and troubleshooting issues.

In addition to my main use case for Red Hat OpenShift, I also use virtualization, including different on-premises systems such as VMware, and we can migrate the VMs to Red Hat OpenShift for management. We can utilize different clusters in Red Hat OpenShift, as every cluster can be installed on our OCP, allowing us to manage them effectively. Red Hat OpenShift proves to be a good product for managing clusters, especially with its easy-to-use console that overlays Kubernetes, providing easy access to workloads, deployment options, and the ability to delete pods. Red Hat recently integrated the console with cloud capabilities, so we can view metrics, graphs, and events in a graphical user interface, eliminating the need to operate everything through the CLI.

The best features Red Hat OpenShift offers include the graphical user interface, which is a significant time-saving feature. There are different roles such as developer and administrator, and we can manage both administrative and developer tasks through the graphical interface that organizes information similarly to how it is executed in the CLI. We can access pod information, metrics, and everything easily, making it accessible even for non-technical users.

This has helped my team significantly by making many tasks easier; for those who are not as familiar with CLI, the graphical user interface is very useful and explanatory. If we need to perform an upgrade or work quickly, we can accomplish these tasks within minutes using the graphical user interface.

Red Hat OpenShift positively impacts my organization by making tasks easier with a consistent emphasis on high availability and reliability while also being cost-effective.

One area for improvement in Red Hat OpenShift is during upgrades, as there is currently no option to revert to a previous version if vulnerabilities or issues arise. I believe that providing such an option or the ability to take a previous snapshot would be beneficial.

Regarding needed improvements, I believe I covered most aspects with the graphical interface. The documentation contains a wealth of information, which continues to improve day by day, but I observe that there are still many concepts that could be elaborated on, and it is well-documented overall.

I have been using Red Hat OpenShift for eighteen months.

Red Hat OpenShift is deployed in my organization in various environments, including on-premises, public clouds such as Microsoft Azure, and in hybrid configurations with different clusters, such as Red Hat OpenShift for AWS.

My advice for others looking into using Red Hat OpenShift is that it is a new but valuable product, particularly suitable for enterprise-level applications.

I believe Red Hat OpenShift will become a significant player in the market. For those who understand its value, it proves to be very useful. My overall rating for this product is eight point five out of ten.

I work for IBM Control, so I work with Red Hat and VMware, both technologies. I am working with OpenShift. I have not worked on Red Hat CloudForms, but I work with OpenShift. I am the integrator. We are creating automation for our customers using OpenShift, and we have implemented Ansible Tower Platform for automating all the system admin tasks.

We create what you call Ansible playbooks, which we execute for automation and deploy across all of our multi-customers within IBM and Control.

I find the resilient infrastructure feature of OpenShift very valuable, as it has no downtime at all.

I find OpenShift to be very scalable.

The initial setup of OpenShift is difficult; it takes a while to set it up. It is difficult to set up OpenShift because of the infrastructure requirements and the customization required to set up the software.

I would advise others looking into using OpenShift that it is a pretty product, widely accepted by customers, easily scalable, and highly reliable, but it should be more user-friendly. I think it should be more user-friendly because many people request assistance setting it up the first time.

I have been working with the solution for three and a half years.

OpenShift is stable. I would say the stability of OpenShift is nine out of ten.

I find OpenShift to be very scalable. I would rate the scalability of OpenShift a nine.

I think the technical support from Red Hat is good. I rate the technical support an eight. The reason for the rating of eight for technical support is that problems arise frequently, and they need to fix those issues, as it is open-source software requiring a lot of customizations.

We actually buy everything with maintenance; when we buy the software, we buy it with maintenance.

The initial setup of OpenShift is difficult; it takes a while to set it up. It is difficult to set up OpenShift because of the infrastructure requirements and the customization required to set up the software. I would rate the initial setup of OpenShift around five.

The initial setup of that solution took us weeks, but now the deployment is completed within days. It took one to ten days to set up OpenShift.

There are twenty-four to twenty-five people involved in the deployment. I think two to three people are architects, along with all the engineers involved.

I would advise others looking into using OpenShift that it is a pretty product, widely accepted by customers, easily scalable, and highly reliable, but it should be more user-friendly. I think it should be more user-friendly because many people request assistance setting it up the first time. I cannot think of any new features that could be added to make the solution better right now. My overall review rating for this solution is eight out of ten.