A few of our organization's customers use VMware Tanzu Mission Control to manage multiple Tanzus and other Kubernetes entities, especially in demilitarized zones. The product is also used for Tanzu cluster provisioning.
It was used for seamless cluster management of Tanzu Kubernetes Grid clusters, providing a user interface for Kubernetes management. PMC serves as the management control plane for TKG, allowing for lifecycle management of the platform. We were an infrastructure service provider. Our primary use case was upgrading the Kubernetes cluster.
The primary objective is ensuring compliance. It assists clients in addressing their security needs and concerns while ensuring compliance with market-specific requirements.
The primary use case includes application modernization. So our customers need to have suitability and backups. So, the DMC helps in achieving those things.
I am using VMware Tanzu Mission Control to verify the different behavior and manage the cluster, such as in EKS with Amazon AWS or WMware. the different end functions or the different functionalities for the compliance, the backup, or the move charge between different clusters. for the general functionality.
Typically, VMware customers who already have a VMware data center and SDDCs in place adopt VMware Tanzu Mission Control to extend their existing infrastructure into Azure or multi-cloud environments and maximize applications. Tanzu Mission Control enables platform teams to centralize Kubernetes operations.
Head Of Infrastructure & Cloud ops at a comms service provider with 10,001+ employees
Real User
2022-09-14T10:46:00Z
Sep 14, 2022
We are just trying to set it up. It's very young at this point in time. We haven't done much. We're still trying to evaluate the scale and at what level it can work. We are currently working with the Tanzu product team, and we are seeing how it can be leveraged specifically for our environment.
We are primarily utilizing it for racking and debugging purposes. However, as we use Mission Control with cluster integration, we are also using it to track our Kubernetes clusters; monitoring our rank, whether a cluster is active or not, which product application is deployed on this cluster, etc.
We use Mission Control for cloud-native developments where the underlying layer is Kubernetes. We do deployments, and we check the code in GitHub and integrate with GitLab. In GitLab, we have the Git Actions, and it triggers the CI/CD pipeline. It's all based on the underlying cloud-native development perspective and the actual deployment in the cloud. It depends on the particular flow from the development environment to the staging environment and the cloud deployment. That's why it's in a hybrid cloud, and we have two deployment topologies. One is vm cloud, and the other is vCloud on AWS. AWS is the public cloud part of it. We also have the Azure Cloud, and Azure is our hybrid cloud environment. This is basically for the use cases around the CI/CD and monitoring the CI/CD cloud-native deployments in the azure cloud. If we have containerized images that have to be deployed in azure cloud, we monitor them using the Tanzu Mission Control.
IT Specialist at a tech services company with 51-200 employees
Real User
2021-02-08T21:53:00Z
Feb 8, 2021
We have clients with different use cases. We have a customer who is a service provider who sells services in the cloud and Kubernetes. Our clients have cloud and on-premises deployments.
VMware Tanzu Platform is designed for cloud-native development and management of Kubernetes, CI/CD processes, microservices, and containerized workloads. It supports deployments both on cloud and on-premises, providing centralized management via Mission Control.
VMware Tanzu Platform offers seamless integration with vSphere, ESX, and vSAN, supporting centralized cluster management and lifecycle management. The platform provides a GUI for monitoring CI/CD pipelines and network policies,...
A few of our organization's customers use VMware Tanzu Mission Control to manage multiple Tanzus and other Kubernetes entities, especially in demilitarized zones. The product is also used for Tanzu cluster provisioning.
It was used for seamless cluster management of Tanzu Kubernetes Grid clusters, providing a user interface for Kubernetes management. PMC serves as the management control plane for TKG, allowing for lifecycle management of the platform. We were an infrastructure service provider. Our primary use case was upgrading the Kubernetes cluster.
The primary objective is ensuring compliance. It assists clients in addressing their security needs and concerns while ensuring compliance with market-specific requirements.
The primary use case includes application modernization. So our customers need to have suitability and backups. So, the DMC helps in achieving those things.
I am using VMware Tanzu Mission Control to verify the different behavior and manage the cluster, such as in EKS with Amazon AWS or WMware. the different end functions or the different functionalities for the compliance, the backup, or the move charge between different clusters. for the general functionality.
Typically, VMware customers who already have a VMware data center and SDDCs in place adopt VMware Tanzu Mission Control to extend their existing infrastructure into Azure or multi-cloud environments and maximize applications. Tanzu Mission Control enables platform teams to centralize Kubernetes operations.
We are just trying to set it up. It's very young at this point in time. We haven't done much. We're still trying to evaluate the scale and at what level it can work. We are currently working with the Tanzu product team, and we are seeing how it can be leveraged specifically for our environment.
We are primarily utilizing it for racking and debugging purposes. However, as we use Mission Control with cluster integration, we are also using it to track our Kubernetes clusters; monitoring our rank, whether a cluster is active or not, which product application is deployed on this cluster, etc.
I use VMware Tanzu Mission Control as a centralized management platform.
We are interested in using this solution as a Container as a Service (CaaS).
We use Mission Control for cloud-native developments where the underlying layer is Kubernetes. We do deployments, and we check the code in GitHub and integrate with GitLab. In GitLab, we have the Git Actions, and it triggers the CI/CD pipeline. It's all based on the underlying cloud-native development perspective and the actual deployment in the cloud. It depends on the particular flow from the development environment to the staging environment and the cloud deployment. That's why it's in a hybrid cloud, and we have two deployment topologies. One is vm cloud, and the other is vCloud on AWS. AWS is the public cloud part of it. We also have the Azure Cloud, and Azure is our hybrid cloud environment. This is basically for the use cases around the CI/CD and monitoring the CI/CD cloud-native deployments in the azure cloud. If we have containerized images that have to be deployed in azure cloud, we monitor them using the Tanzu Mission Control.
We have clients with different use cases. We have a customer who is a service provider who sells services in the cloud and Kubernetes. Our clients have cloud and on-premises deployments.