Cloud Consumption Interface setup and configuration

CCI is available to VMware Aria Automation on-premises users who want to manage and consume all the Kubernetes-based, desired state IaaS APIs that are available in the vSphere platform using a single, unified consumption interface.

With a cloud-intuitive user interface, a Kubernetes command-line kubectl plugin, and APIs, CCI provides multiple ways for enterprises to develop modern applications with increased agility, flexibility, and to develop modern techniques on vSphere while maintaining infrastructure control.

Enabling the Cloud Consumption Interface

Before a user can use CCI to consume vSphere Kubernetes resources, a VMware Aria Automation administrator must configure access to CCI. The following summary describes the main configuration steps. Cross references provide the details for each step.

• Enable one or more Supervisor clusters by configuring applicable Supervisor clusters. See Configuring and Managing a Supervisor.

  For information about Supervisor clusters and Namespaces and how they work with vSphere and Tanzu, see VMware vSphere with Tanzu Documentation.

• CCI requires that usernames include the users' domains. To satisfy the requirement, ensure that Workspace ONE Access uses userPrincipalName, not sAMAccountName, as the directory search attribute.
• Configure CCI Supervisor Service Single Sign-On (SSO). See Setting Up Single Sign-On for CCI.
• Set up the CCI command line interface (CLI) by downloading the kubectl plug-in. See Preparing to use the Command Line Interface to perform CCI tasks.
• Add a vCenter Server cloud account in Automation Assembler.

  See Create a basic vCenter cloud account in VMware Aria Automation.

• Use the kubectl CCI CLI to set up CCI components so that they are available to project users. See Setting up the Cloud Consumption Interface infrastructure using kubectl.