The Getting Started with VMware Tanzu Mission Control documentation provides a series of simple tasks to help you get started with Tanzu Mission Control. The tasks introduce you to some common features in Tanzu Mission Control to manage your Kubernetes clusters and other resources. Doing the tasks also familiarizes you with the Tanzu Mission Control console.
Follow the procedures sequentially. However, if you don’t want to provision new clusters from within Tanzu Mission Control, you can skip the sections describing how to connect a cloud provider account and create a cluster.
Getting access and launching Tanzu Mission Control
Use Tanzu Platform cloud services tools to gain access to VMware Tanzu Mission Control. After you get access, log in to the Tanzu Mission Control console to start managing clusters.
Create a cluster group to help organize and manage your clusters.
Attach a cluster, if you already have one, to your VMware Tanzu Mission Control organization.
Connecting a cloud provider account
Set up a cloud provider account connection in VMware Tanzu Mission Control so you can start creating clusters. This procedure walks you through the process of creating a cloud provider account connection with AWS using Role ARN.
Provisioning a new EKS cluster
Use the Tanzu Mission Control console to create a new Kubernetes cluster in your cloud provider account.
Connect to your provisioned cluster with kubectl
.
Run a deployment in your cluster.
Exercise the observability features of VMware Tanzu Mission Control to examine what is happening in your cluster.
This information is intended for administrators who want to use Tanzu Mission Control to create and manage Kubernetes clusters and their associated resources. This information is also intended for application administrators and developers who want to use Tanzu Mission Control to deploy and manage modern apps in a Kubernetes architecture. The information is written for developers who have a basic understanding of Kubernetes and are familiar with container deployment concepts. In-depth knowledge of Kubernetes is not required.