The vSphere with Tanzu platform involves two roles, the vSphere administrator and the DevOps engineer. Both roles interact with the platform through different interfaces and can have users or user groups defined for them in vCenter Single Sign-On with associated permissions. The workflows for the vSphere administrator and DevOps engineer roles are distinct and determined by the specific area of expertise these roles require.

User Roles and Workflows

As a vSphere administrator, the primary interface through which you interact with the vSphere with Tanzu platform is the vSphere Client. At a high level, your responsibilities involve configuring a Supervisor Cluster and namespaces, where DevOps engineers can deploy Kubernetes workloads. You should have excellent knowledge about the vSphere and NSX-T technologies, and basic understanding about Kubernetes.

Figure 1. vSphere Administrator High Level Workflow

vSphere Administrator High Level Workflow

As a DevOps engineer, you might be a Kubernetes developer and an application owner, a Kubernetes administrator, or combine functions of both. As a DevOps engineer, you use kubectl commands to deploy vSphere Pods and Tanzu Kubernetes clusters on existing namespaces on the Supervisor Cluster. Typically, as a DevOps engineer, you do not need to be an expert on vSphere and NSX-T, but have basic understanding about these technologies and the vSphere with Tanzu platform to interact with the vSphere administrators more efficiently.

Figure 2. DevOps Engineer High Level Workflow

DevOps Engineer High Level Workflow

Supervisor Cluster with NSX-T Data Center Workflow

As a vSphere administrator, you configure the vSphere with Tanzu platform with the necessary compute, storage, and networking components. You can use NSX-T Data Center as a the networking stack for Supervisor Cluster. For more information about the system requirements, see System Requirements and Topologies for Setting Up a Supervisor Cluster with NSX-T Data Center.

Figure 3. Supervisor Cluster with NSX-Data Center Networking Workflow

Initial Platform Configuration Workflow

Supervisor Cluster with vSphere Networking Stack Workflow

As a vSphere administrator, you can configure a vSphere cluster as a Supervisor Cluster with the vSphere networking stack. For more information about the system requirements, see System Requirements and Topologies for Setting Up a Supervisor Cluster with vSphere Networking.
Figure 4. Supervisor Cluster with vSphere Networking Stack Configuration Workflow
Supervisor Cluster with vSphere Networking Stack Configuration Workflow

Namespace Creation and Configuration Workflow

As a vSphere administrator, you create and configure namespaces on the Supervisor Cluster. You must gather specific resource requirements from DevOps engineers about the applications they want to run and configure the namespaces accordingly. For more information see, Working with Namespaces on a Supervisor Cluster.

Figure 5. Namespace Configuration Workflow

Namespace Configuraiton Workflow

vSphere Pod Workflow

As a DevOps engineer, you can use the vSphere Pod Service to run your applications. The vSphere Pod Service creates vSphere Pod on the Supervisor Cluster. For more information, see Working with vSphere Pods.

Figure 6. vSphere Pods Workflow

vSphere Pods Workflow

Tanzu Kubernetes Cluster Workflow

As a DevOps engineer, you create and configure Tanzu Kubernetes clusters on a namespace created and configured by your vSphere administrator. For more information, see #GUID-DBF5D8F2-2A28-4730-8AA3-32E9CE1C3BB8.

Figure 7. Tanzu Kubernetes Cluster Workflow

Tanzu Kubernetes Cluster Workflow