# Introducing VMware Tanzu Mission Control

VMware's Tanzu Mission Control aims at providing a centralized platform to deploy, manage, and secure multiple Kubernetes cluster. Tanzu Mission Control provides a way Provision new clusters or bring in existing Kubernetes Clusters. It offers a Policy Engine that automates Access control and Security policies across a fleet of clusters. Tanzu Mission Control abstracts away individual IAM, infrastructure provisioning constructs from various cloud providers to bring a more simplified platform. 

![Tanzu Mission Control: Deploy, Manage and Secure Multiple Kubernetes Cluster](/files/-M20MfrpNc54TK6Yq4E3)

For example, an Organization wanting to deploy a Kubernetes Cluster in AWS and vSphere will have to work with different compute, network and storage entities in each of these environment to deploy Clusters. Kubernetes Nodes in AWS can be created using EC2 instances, whereas the same needs a OVA/VM template in vSphere. Similarly, to provide networking services to the cluster, a VPC and ELB will have to be carved out in AWS and in vSphere it would be virtual networks and load balancers. Beyond the provisioning aspects, giving users from an Identity source like Active Directory will mean federating access to AWS IAM and vSphere roles for each cluster. 

Tanzu Mission control simplifies all the various aspects of provisioning and managing Kubernetes clusters across various environments. For Provisioning and Lifecycle management, Tanzu Mission control uses the Open Source Project [`Cluster-API`](https://github.com/kubernetes-sigs/cluster-api).Cluster-API uses objects like machines and providers to abstract cluster components and infrastructure. 

Tanzu Mission Control then brings in unified Identity and Access control into these environments by working with VMware's Cloud Services and mapping users and groups to Kubernetes clusters and role bindings. 

Go through the video below to get an overview on Tanzu Mission Control

{% embed url="<https://youtu.be/BqBQllgl8T4>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tanzu-solutions.gitbook.io/cloud-native-solutions/introducing-vmware-tanzu-mission-control.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.