Amazon Elastic Kubernetes Service (EKS) vs. Red Hat OpenShift on IBM Cloud

Well suited for microservices architecture but can be a bit costly if less number of microservices or monolithic architecture hosted to be hosted on containers. Use of hybrid cluster instances also works well using both normal and fargate instances. Also the integration of audit and diagnostic logs of master nodes helps to reduce the unwanted access related issues.

Incentivized

RedHat OpenShift is not only suited for IBM Cloud but can run in ANY cloud. We installed in Azure Cloud, for example. It can also run on Linux servers or a Power 9 machine. It is built for multi-cloud or on-prem environments. IBM support provides such excellent guidance in the installation and configuration that no other product on the market can beat it.

Incentivized

• Upgrade the kubernetes clusters to the latest version with a single click
• Auto scaling policies to automatically scale the nodes
• Detailed logs and events on the cluster within the EKS clusters portal, cloudwatch logs and metrics

Incentivized

• Multiclick provisioning of resources makes it super easy to manage pods and deployments. We don't have to maintain code for the same
• In built security features and customizability ensures that organization wide standards are integrated well into the containers
• Automated backups, scale ups and fail recovery makes sure of minimal down time

Incentivized

• AWSIAM integration with Kubernetes RBAC could be better.
• Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
• EKS bootstrap time could be faster ...

Incentivized

• I wish it had better compatibility with docker file syntax. We had issues when it couldn't build standard docker files
• Wish it had better documentation
• Wish they offered fully supported client libraries for the Openshift API rather than dumping it on a 3rd party

Incentivized

Cluster maintanence is reduced, easier to deploy resources, great observability insights

Incentivized

I think response time for IBM Cloud support should be improved.

Incentivized

It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.

Incentivized

We evaluated a number of potential solutions and ultimately chose Red Hat OpenShift because it was compatible with our existing technology. Time and costs savings have been realized throughout the company since we implemented Red Hat OpenShift, and the IT department has been freed up to focus on activities that are more valuable.

Incentivized

• Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure.
• EKS Upgrade process to a new version seems to be taking very long ....
• EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes.

Incentivized

• Our customer satisfaction and NPS score has had positive outcomes based on new architecture
• We are focused on business outcomes vs running the service and maintenance
• OpenShift on IBM Cloud has had a direct, positive impact on TCO, ROI, and payback period
• Our staff is more focused on higher-level business activities, i.e. acquiring & customer retention

Incentivized