Item: Red Hat OpenShift
Rating: 10
Author: Matias Mospan

Overall Satisfaction with Red Hat OpenShift

Use Cases and Deployment Scope

As a Red Hat Partner we use OpenShift to help our customers to include it in their projects as the main platform for running workloads. Most of the business problems that they solve are regarding agility for deployment and managing scalability for better Customer Experience, better performance and easy rollout. Another business problems that some custormers face that solve with openshift is the portability either from infrastructure or from environments.

Pros and Cons

Pros

Compatibility with most of the infrastructure providers (public or private clouds) and the installations methods
User Exprience in the console and the integration between components
The management of operators
The separation on Dev Experience and Admin Experience in the console

Cons

The observability stack still looks like it's separated from the rest of the console. Need to be more integrated like providing a feature that will make "easy" todo customize some dashboards
The migration between versions in clusters that include a lot of operators sometimes is really risky because of the versions compatilbility

Return on Investment

Negative on SMB, the "starter kit" is big for most of the SMB (at least in LATAM)
Positive on the integration of components, could become the main PaaS really easy

Support Rating

Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com.

Key Insights

Do you think Red Hat OpenShift delivers good value for the price?

Yes

Are you happy with Red Hat OpenShift's feature set?

Yes

Did Red Hat OpenShift live up to sales and marketing promises?

Yes

Did implementation of Red Hat OpenShift go as expected?

Yes

Would you buy Red Hat OpenShift again?

Yes

Usability

As I said before, the obserability is one of the weakest point of OpenShift and that has a lot to do with usability. The Kibana console is not fully integrated with OpenShift console and you have to switch from tab to tab to use it. Same with Prometheus, Jaeger and Grafan, it's a "simple" integration but if you want to do complex queries or dashboards you have to go to the specific console

Contract Terms and Pricing Model

It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.

Likelihood to Recommend

Best suited: When starting new developments you have the opportunity to design and think the application to be fully "cloud native" and if you could manage that, OpenShift is teh best platform to developers and then to run the workloads. Less appropiate: When your organization still use old software architectures patterns and some monolotics apps need to be "agilized". Some of the points of OpenShift is that you could "use it for ols monolith" but I saw that the learning path is really long for some roles and it's really difficult to do the sizing of the that kind of apps.

Red Hat OpenShift Feature Ratings

Comments

Please log in to join the conversation

OpenShift Review

Software Version