I recently deployed the Local Consumption Interface (LCI) which is a new vSphere IaaS (formerly vSphere with Tanzu) Control Plane Service that was just introduced with the release of vSphere 8.0 Update 3 into my homelab.
Successfully deployed the new vSphere IaaS (formally vSphere w/Tanzu) Local Consumption Interface (LCI) Service https://t.co/1fbTUiNjJd
Needed to refer to docs to figure out how to actually access the LCI UI, its under Resources within vSphere Namespace! #vSphere80U3 pic.twitter.com/Wu9afjzVx6
โ William Lam (@lamw.bsky.social | @*protected email*) (@lamw) July 7, 2024
While going through the manual vSphere UI deployment, I noticed there were only handful of vSphere IaaS services that are shipped out of the box including the VM Service (VM Operator), Velero vSphere Operator and Tanzu Kubernetes Grid (TKG) Service.
The workflow to register a new vSphere IaaS service is not difficult, but it does take multiple steps from downloading the deployment YAML file, uploading the file to vCenter Server and then confirm the deployment before the deployment of the service begins and this would have to be done for each vSphere IaaS service you wish to deploy!
There has to be a better and more streamline way, especially for those that do not like to click to many times in the UI ๐