We compared VMware Tanzu Mission Control and OpenShift Container Platform based on our user's reviews in several parameters.
VMware Tanzu Mission Control and OpenShift Container Platform both offer competitive pricing, efficient setup processes, and positive customer service experiences. VMware Tanzu Mission Control is praised for its management capabilities, multi-cloud deployment, and security measures, while OpenShift Container Platform is lauded for its system integration, resource management, and application scalability. Users suggest VMware Tanzu Mission Control could improve on user interface and performance, while OpenShift Container Platform could enhance UI, system performance, resource management, and language support.
Features: VMware Tanzu Mission Control offers comprehensive management capabilities, multi-cloud deployment, resource utilization, user-friendly interface, security measures, and automation. OpenShift Container Platform focuses on integration, resource management, security, customization, and scalability of applications.
Pricing and ROI: The setup cost for VMware Tanzu Mission Control is minimal and straightforward, with no additional complexities. The licensing process is hassle-free and transparent, allowing flexibility for various deployment scenarios. In comparison, the setup process for OpenShift Container Platform is also straightforward and efficient. The licensing model is commended for its flexibility in meeting the needs of different users., In terms of return on investment, VMware Tanzu Mission Control has proven to be valuable for managing and controlling VMware ecosystems. Users reported improved efficiency and resource allocation. On the other hand, OpenShift Container Platform offers significant improvements in resource utilization, scalability, efficiency, and cost savings. It has enabled increased productivity and revenue growth through optimized operations and streamlined workflows.
Room for Improvement: VMware Tanzu Mission Control has room for improvement in terms of user interface, performance, documentation, and customization options. OpenShift Container Platform, on the other hand, could benefit from enhancements in user interface, system performance, resource management, and support for different programming languages.
Deployment and customer support: In comparing the reviews, it can be concluded that the duration to establish a new tech solution with VMware Tanzu Mission Control typically takes one week for both deployment and setup phases, while with OpenShift Container Platform, it can range from one week for both phases to three months for deployment and an additional week for setup. The context in which these terms are used must be carefully evaluated., The customer service for VMware Tanzu Mission Control has been highly praised for being excellent, top-notch, and responsive. Users appreciate the promptness and efficiency of the support team. OpenShift Container Platform also receives positive feedback, with users valuing the promptness, responsiveness, and expertise of the support staff. Overall, users express satisfaction with the customer service experience provided by both platforms.
The summary above is based on 39 interviews we conducted recently with VMware Tanzu Mission Control and OpenShift Container Platform users. To access the review's full transcripts, download our report.
"The platform is easy to scale as it supports Windows worker node."
"I think it's a pretty scalable tool...The solution's technical support has been pretty good."
"Dashboards... give us all the details we need to see about the microservices."
"The most valuable feature for me in the OpenShift Container Platform is the option to manage different containers and environments and also being able to switch among them."
"The stack in the software supply chain is one of the main reasons that we use OpenShift. When I came to this company, we bought hardware from IBM named Bluemix, and they used ICP, which stands for IBM Cloud Private."
"The auto scalability feature, which is based on smart agendas, determined from pre-prepared rules is the most valuable feature. You can also create different routes for deployment. Deployment types can be provided with an identifier, such as an ARB deployment. This really helped in rolling out releases without disrupting services for the end-users."
"Some of the primary features we leverage in the platform have to do with how we manage the cluster configurations, the properties, and the auto-scalability. These are the features that definitely provide value in terms of reducing overhead for the developers."
"Openshift is a very developer-friendly product."
"I have multiple Kubernetes environments within my environment. TMC gives me a single pane view, which is good for managing everything."
"The initial setup is easy."
"The most popular feature of VMware Tanzu Mission Control is its graphical user interface for describing network policies on the Service Mesh, which is highly integrable with other tools commonly used in supply chains such as security."
"The multi-tenancy with the VCD is great."
"A feature we find valuable is that other products can also be integrated with Mission Control. This means that we can see the status of specific clusters, as well as view the monitoring application logs all from one point."
"VMware Tanzu Mission Control has many valuable features, such as ease of use and customization."
"The most important thing about the solution is its flexibility."
"Tanzu Mission Control has quite a set of rich features when compared to OpenShift."
"It is difficult to deploy the OpenShift cluster in a bare-metal environment."
"OpenShift has a pretty steep learning curve. It's not an easy tool to use. It's not only OpenShift but Kubernetes itself. The good thing is that Red Hat provides specific targeted training. There are five or six pieces of training where you can get certifications. The licenses for OpenShift are pretty expensive, so they could be cheaper because the competition isn't sleeping, and Red Hat must take that into account."
"OpenShift needs to improve their container storage."
"OpenShift has certain restrictions in terms of managing the cluster when it's running on a public cloud. For example, identity and access management integration with the IM of AWS is quite difficult. It requires some open-source tools to integrate. This is one area where I always see room for improvement."
"In my experience, the issues are not always simply technical. They do stem from technical challenges, but they struggle with the topic of adoption. When you encounter all of the customer pull, there are normally several tiers of your client pop that can adopt either the fundamental features or a little more advanced ones. The majority of the time, the challenge is determining how to drive adoption, how to sell the product to the customer, and how much time they can spend to really utilize those advanced features. If we get into much more detail, but this is from my perspective as the platform engineer and not the end customer, the ability of the end user to be able to debug potential issues with their application That is arguably the most important, let's say, work throughput in my area."
"It has an option to install OpenShift without connecting it to the Internet. We tried this, but it was very hard. We couldn't manage to use that option. We wanted to use it offline for installations, updates, upgrades, etc., but we didn't find the offline installation and updates easy. This could be better."
"Setting up OpenShift isn't easy. I rate it three out of ten for ease of setup. We're deploying it in three phases. They're in the second phase now. The total deployment time will be five months. We expect to complete the deployment this March. There are 13 people on three teams working on this deployment."
"The UI could be more user-friendly to drive tasks more effectively through the interface."
"This product doesn't have a GUI. In order to use it properly, I need to connect it to a new GUI or build a GUI to manage it — it's pretty difficult."
"The disaster recovery feature could be improved to provide better tracking of issues. I would also like to see the introduction of a dashboard view, for even further integration of all the areas that Mission Control looks at."
"The infrastructure is quite challenging."
"The network control and security policies must be improved."
"Having a unified dashboard to manage all infrastructure, whether it involves additional IT infrastructure or modern apps, would be highly advantageous"
"The solution could improve by having better integration with other solutions such as HPE."
"LYNX is a managed cluster solution that takes care of specific details within a cluster, such as sequences or services. I haven't seen this feature in Tanzu Mission Control."
"Another area of improvement is pricing."
OpenShift Container Platform is ranked 1st in Container Management with 36 reviews while VMware Tanzu Mission Control is ranked 3rd in Container Management with 12 reviews. OpenShift Container Platform is rated 8.2, while VMware Tanzu Mission Control is rated 7.8. The top reviewer of OpenShift Container Platform writes "Provides automation that speeds up our process by 30% and helps us achieve zero downtime". On the other hand, the top reviewer of VMware Tanzu Mission Control writes "Gives a single pane to manage multiple Kubernetes environments and has competitive pricing". OpenShift Container Platform is most compared with Amazon EKS, Nutanix Kubernetes Engine NKE, Amazon Elastic Container Service, Rancher Labs and Kubernetes, whereas VMware Tanzu Mission Control is most compared with Rancher Labs, Kubernetes, Nutanix Kubernetes Engine NKE, Amazon EKS and Docker. See our OpenShift Container Platform vs. VMware Tanzu Mission Control report.
See our list of best Container Management vendors.
We monitor all Container Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.