vRealize Automation Cloud Assembly offers several options for managing and deploying Kubernetes resources.

There are two primary options to working with Kubernetes resources in vRealize Automation Cloud Assembly. You can integrate VMware Tanzu Kubernetes Grid Integrated Edition (TKGI), formerly PKS, or Red Hat OpenShift with vRealize Automation Cloud Assembly to configure, manage and deploy Kubernetes resources. With the second option, you can leverage a vCenter cloud account to access supervisor namespaces to work with vSphere Project Pacific Kubernetes-based functionality.You can also integrate external Kubernetes resources in vRealize Automation Cloud Assembly.

Working with VMware Tanzu Kubernetes Grid Integrated Edition (TKGI) or Openshift Integrations

For TKGI, external clusters, or Openshift configurations, vRealize Automation Cloud Assembly provides a Kubeconfig that enables users to access applicable Kubernetes clusters.

After you create a TKGI or OpenShift integration, applicable Kubernetes clusters become available in vRealize Automation Cloud Assembly and you can add and create Kubernetes components to vRealize Automation Cloud Assembly to support management of cluster and container applications. These applications form the basis of self-service deployments that are available from the Service Broker catalog.

Working with vSphere Project Pacific Kubernetes Clusters

Project Pacific is a vSphere enhancement that uses Kubernetes as its control plane. It enables you to manage both virtual machines and containers from one interface. vRealize Automation Cloud Assembly enables users to leverage the Pacific Kubernetes capabilities that have been embedded within vSphere. You can access Pacific functionality by creating an integration with a vCenter deployment with a vSphere implementation that contains supervisor clusters. Pacific enables you to manage both conventional virtual machines and Kubernetes clusters from vCenter.

For Pacific-based supervisor namespaces, users must have access to an applicable vSphere SSO so that they can log in to a provided link to the supervisor namespace details. Then, they can download a customized Kubectl with vSphere authentication so they can use their supervisor namespace.

To use this functionality, you must have a vCenter with vSphere cloud account that has supervisor namespaces configured. After a users has logged in they can begin working with applicable namespaces.