What is your primary use case for OpenShift?

We help some operators implement the container platform. Some of the operators use other software, such as VMware or Whitestack. Our focus is on pushing Red Hat products. We also use OpenShift for containerized applications in IT and networks, including applications like My Mobistar, My Carlos, and Smart Wi-Fi.

We use the product primarily for CI/CD activities across different platforms using Argo CD and Tekton to deliver applications.

We use Red Hat OpenShift for runtime or application migration, transitioning from classic application servers and configuration restore machines.

OpenShift works as a data pipeline management tool.

We use OpenShift for the deployment of microservices architecture and containerizing applications.

I use the solution for deployments with Java applications in the environment.

We use the solution to split monolithic into microservices. I mostly use OpenShift as a Kubernetes distribution.

We're going to deploy the entire core banking of the bank on the platform.

Usually, we use it as a test environment and to quickly develop the proof of concept for various projects. So, it's mainly for quick deployment and testing. It's deployed on the cloud and on-premises.

OpenShift is a containerization platform.

We have deployed OpenShift on-premises on VMware and Azure, but not the managed platform. We manage the deployment ourselves, doing our own customizations.

We use the solution to run our own software. Our software is different from the banking system, and it's mostly written in Java with a backend, an Angular frontend, MongoDB, and some caches.

We use this solution as part of our containerization so that we can manage different applications in the system. We use it to make the CICD pipeline and integrations smoother.

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

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.

We use the solution for container orchestration and management.

We are using OpenShift as a microservice platform.

We are not using it for our core banking or any critical application. It's just for our remediation services. We have an ITSM tool, which is running on that, et cetera.

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.

Our company uses it as a platform as a service. We have business units with developers who deploy their containerized applications in OpenShift. We have a team that supports the infrastructure of clusters all over the world. We run thousands of applications on it. It's deployed on-prem and in the cloud.

We use OpenShift mainly for building middleware services and web applications. All the applications we have transformed on the microservices architecture have been deployed on OpenShift.

I have used OpenShift in two companies. My earlier company was using a CI/CD pipeline. I customized the CI/CD pipeline in Java and then in Jenkins. We used it to deploy applications in different stages in the CI/CD. In my current company we are using CloudBees Core. They have a CI/CD pipeline and using that we deploy with the OpenShift platform. If any application team wants to deploy an application on a container platform, we offer a platform for that. If they want to deploy a microservice application and they want to use a microservices architecture, we provide a space for that. OpenShift is running on the AWS platform, which means that deployment is highly scalable and highly retainable. People who want to deploy an application with a zero-downtime infrastructure prefer using the to OpenShift platform.

We're using this solution for newly developed applications in house development applications. I'm an infrastructure architect and we are customers of Open Shift.

Our primary use case is to move applications to OpenShift in order to remove legacy solutions.

We have a PaaS solution built on OpenShift with more templates and shared services for a containerized application environment. So, the solution built will be using PaaS that is built on Openshift and hosted in a hybrid PaaS (dedicated & AWS) for building, deploying, and managing microservices-based applications. We will be using many features of OpenShift for scalability, availability, and security (TLS/OAuth, IdAM integration).

Used for multiple environments and clients. Providing details is not possible due to NDA constraints. This main purpose of this kind of Platform is a Production grade Environment where Data Protection and Release Management is managed by the Service Provider.

OpenShift is a primary tool in my daily work and in the project I have been working on in recent years – TV streaming services used widely in the U.S. and outside. OpenShift is used for intensive DevOps and running pieces of the project adhering to the microservices architecture. The project's architecture includes physical servers in tens of datacenters. OpenShift plays a central role in developing, testing, and running specific software.