One of the valuable features is that it's very easy to package an application and deploy it within a short period of time. Since it will be in the CI/CD pipeline, deployment is very easy. And the automation process is very easy and it's highly scalable. It can be scaled up or down at any time. We don't need a person managing the infrastructure all the time because there is automatic self-healing of the application in case something goes wrong.

The developers seem to like the source-to-image feature. That makes it easy for them to deploy an application from code into containers, so they don't have to think about things. They take it straight from their code into a containerized application. If you don't have OpenShift, you have to build the container and then deploy the container to, say, EKS or something like that. It's a little different.

In terms of the solution’s security throughout the stack and the software supply chain, it meets our needs. It's excellent as far as we're concerned. It goes right along with the Kubernetes role-based assets control. OpenShift's security features for running business-critical applications are excellent. A lot of our external-facing applications have been protected. We do use Apigee for a lot of it, but we also do security scans so we don't expose something to a known vulnerability.

The self-healing of pods is a valuable feature. This feature goes a long way in helping us ensure our uptime for services, improving the performance of the system.

The solution provides us with the flexibility of cloud-native stacks while enabling us to meet regulatory constraints. Since most of our services were deployed on-premises, this allowed us not to get into data privacy issues for services with personally identifiable information belonging to customers. It is microservice-ready from a cloud-native perspective, which is a benefit.

With the automation that OpenShift gives you, you can automate as much as possible. This goes a long way in reducing time to market and errors due to human intervention. So, if an organization can do a lot of automation, e.g., automating deployments, that can go a very long way in reducing the time to market and the time required to fix issues that arise out of deployment.

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.

The support is very strong in Turkey. We are very happy with its capabilities. The steps are easy in terms of usage.

The most valuable feature of OpenShift is the containers.

I think the most valuable feature this solution provides is the possibility to have support throughout the whole platform, including logging, monitoring, op features, and the like. It's a simple solution.