Red Hat Openshift is ideal for organizations using microservices and cloud environments. I like that the platform is auto-scalable, which saves overhead time for developers. I think Openshift can be a great alternative for a fully managed container technology that will work both on premises and in the cloud.
OpenShift simplifies the management of Kubernetes clusters for our developers. It is very simple to use, so even our new hires can manage it easily.
The security of RedHat is comprehensive - we don’t need to worry about patching manually since we can update the entire environment together with the security patches.
Some disadvantages I see in using OpenShift are that effectively using OpenShift to move from on-prem to the cloud requires a steep learning curve and there is not much documentation explaining how to do it.
VMware Tanzu provides a centralized control center for Kubernetes via scalability and consistent security policy management.
The easy integration of VMware Tanzu with other products is one of the features I like most. I like that you don’t need to integrate it manually with different vendors. The multitenancy and graphic interface simplify managing the containers.
One disadvantage I can find in VMTanzu is that it needs to incorporate new security essentials such as supporting zero-trust architecture. Another con is that it requires a high level of Linux knowledge to make the most of it.
Despite RedHat claiming to be designed for hybrid environments, in reality, it requires a lot of knowledge to manage it properly from cloud to on-premises and back. VMware Tanzu is a better option when it comes to easy integration and scalability.
Digital Solution Technical Analyst at ADIB - Abu Dhabi Islamic Bank
Nov 3, 2020
From a networking perspective, the routing capability can be matured further. OpenShift doesn't handle restrictions on what kind of IPs are allowed, who can access them, and who cannot access them. So it is a simple matter of just using it with adequate network access, at the network level. It should be possible to whitelist IPs so that you can allow and restrict access to the API. That would be a fantastic feature. OpenShift would then encapsulate the entire security and access. This is one improvement that I would seriously want our client to have, and for that reason, I have joined the OpenShift community, and it is a project I could probably work on myself. The second thing is that deployment is more of a strategy rather than a feature in OpenShift. Although you can create different routes, and it works fine, it is not an innate feature of OpenShift that it understands that you want to run specific versions of the same service as needed.
CTO and Principal Architect at Li9 Technology Solutions
Nov 13, 2020
The solution has pretty good features overall. I can't recall if there are any that are lacking. The pricing is quite high. It would be nice if they could make it more competitive. The solution needs to introduce open ID connect integration for role-based access control.