Quickstart for the Tanzu Mission Control Plug-ins in the Tanzu CLI

This topic shows how to use some commonly used commands in the Tanzu Mission Control plug-ins.

All non-core commands in the tanzu CLI require that you specify the context for the command. For example, the following command uses the cluster plug-in from your context in the mission-control target.

tanzu mission-control cluster list

Before you begin

Before you can use the tanzu command-line interface, make sure you have already downloaded, installed, and initialized the CLI binary, as described in Install and Configure the Tanzu CLI and Tanzu Mission Control Plug-ins.

Create a context for Tanzu Mission Control

tanzu context create  --endpoint <my-endpoint> 

For example:

tanzu context create  --endpoint my-org.tmc.cloud.vmware.com 

Verify your new context

tanzu context list

Use your new context

tanzu context use my-new-context

Verify your new context again

tanzu context list

The output from this command shows that your new context is the active context, for example:

Target:  kubernetes
  NAME  ISACTIVE  ENDPOINT  KUBECONFIGPATH  KUBECONTEXT
Target:  mission-control
  NAME            ISACTIVE  ENDPOINT
  my-new-context  true      my-org.tmc.cloud.vmware.com:443

Sync the Tanzu Mission Control plug-ins

tanzu plugin sync

Verify your updated plug-ins

tanzu plugin list

List the clusters your organization that are managed by Tanzu Mission Control

tanzu mission-control cluster list

List the workspaces your organization

tanzu mission-control workspace list

Install a specific plug-in through discovery from your active Tanzu Mission Control endpoint

tanzu plugin install cluster --target mission-control

Create a cluster from a configuration file

tanzu mission-control cluster create -f <config-file> 

Create a cluster from a template

tanzu mission-control cluster create --template <template-name> -v <values-file>

Note: Creating a resource with a template requires the values file. A values file contains the input parameters in a key/value format. A list of inputs required by the template and the schema for the value are defined in the input section.

Get a list of available templates

tanzu mission-control cluster template list

Get a named template

tanzu mission-control cluster template get <template-name>

Note: You can list the input fields accepted by a given template using the following command:

tanzu mission-control cluster template get <template-name> | grep field

Get a cluster

tanzu mission-control cluster get <cluster-name> -m <management-cluster-name> -p <provisioner-name>

Get a kubeconfig file to access an attached cluster

tanzu mission-control cluster kubeconfig get <cluster-name>

Get a kubeconfig file to access a provisioned cluster

tanzu mission-control cluster admin-kubeconfig get <cluster-name> -m <mgmt-cluster-name> -p <provisioner-name>

Delete a plug-in

tanzu mission-control plugin delete <plug-in-name>