As a vSphere administrator, you must give your DevOps users access to a source of VM templates, so that the DevOps engineers can use the templates to provision new stand-alone VMs in the vSphere with Tanzu environment. To give the access, add a content library that contains VM templates to the namespace.
- Create a content library. See Create a Content Library for Stand-Alone VMs in vSphere with Tanzu.
- Populate the library with VM templates. See Populate a Content Library with VM Images for Stand-Alone VMs in vSphere with Tanzu.
- In the vSphere Client, go to the namespace.
- From the vSphere Client home menu, select Workload Management.
- Click the Namespaces tab and click the namespace.
- Add a content library.
- On the VM Service pane, click Add Content Library.
- Select one or several content libraries and click OK.
Contents of the library you added become available in the Kubernetes namespace as VM images and can be used by DevOps to self-service VMs. See Deploy a Virtual Machine in vSphere with Tanzu.
What to do next
After you associate a content library with a namespace, you can add more content libraries or remove the library to unpublish it from the Kubernetes namespace. See Manage VM Content Libraries on a Namespace in vSphere with Tanzu.