To provision a Tanzu Kubernetes cluster in an internet restricted ("air-gapped") environment, create a local content library and manually import each Tanzu Kubernetes release.
- vCenter Server instance where you want to create the library. or on the
- on the destination datastore.
- Log in to the vCenter Server using the vSphere Client.
- Click Menu.
- Click Content Library.
- Click Create.
The system displays the New Content Library wizard.
- Specify the Name and location of the content library and click Next when you are done.
Field Description Name Enter a descriptive name, such as TanzuKubernetesRelease-local. Notes Include a description, such as Local library for Tanzu Kubernetes releases vCenter Server Select the vCenter Server instance where vSphere with Tanzu is enabled.
- At the Configure content library page, select the Local content library option and click Next.
As described below, for local content libraries you manually import the OVF templates you want to use.Note: To use a Subscribed Content Library, see Create, Secure, and Synchronize a Subscribed Content Library for Tanzu Kubernetes releases.
- Configure the OVF security policy at the Apply security policy page and click Next when you are done.
When you select this option, the system verifies the OVF signing certificate during the synchronization process. An OVF template that does not pass certificate validation is marked with the Verification Failed tag. The the template metadata is kept, but the OVF files cannot be synchronized.Note: Currently the OVF default policy is the only supported security policy.
- Select Apply Security Policy
- Select OVF default policy
- At the Add storage page, select a datastore as a storage location for the content library contents and click Next.
- On the Ready to complete page, review the details and click Finish.
- At the Content Libraries page, select the new content library you created.
- Download the OVA files for each Tanzu Kubernetes release you want import to the local content library.
Note: If the certificate and manifest file are not available in the source directory during the import process, the imported library item will not be usable. This means that for a local content library configured with a security policy, all four required files must be in the local directory from where the ovf and vmdk are imported. In addition to the ovf and vmdk files, you also need to download the cert and manifest files and put all four files in the same source directory.
- Using a browser, navigate to the following URL:
- Click the directory for the image you want. Typically this directory is the latest or most recent version of the Kubernetes distribution.
ob-18186591-photon-3-k8s-v1.20.7---vmware.1-tkg.1.7fb9067Note: The distribution name is needed to import the files to the local content library, so you might want to copy it to a file or keep the browser open until you complete the procedure.
- For each of the following files, right-click and select Save link as.
- Verify that each file successfully downloads to your local file system.
- Import the OVA files to the local content library.
- Select .
- From the list of Content Libraries, click the link for the name of the local content library you created.
- Click Actions.
- Select Import Item.
- In the Import Library Item window, select Local File.
- Click Upload Files.
- Select both files
photon-ova-disk1.vmdk.You see the message
2 files ready to import. Each file is listed with a green check mark beside its name.
- Change the Destination Item name to be the Photon image version plus the Kubernetes version from the directory where you downloaded the files.
- Click Import.
- Verify that the local content library is populated with the Tanzu Kubernetes release.
- Reveal the Recent Tasks pane at the bottom of the page.
- Monitor the task Fetch Content of a Library Item and verify that it is successfully Completed.
- In the local content library, select .
- Verify that the Tanzu Kubernetes release metadata is listed and its content is stored locally.
What to do next
Configure each vSphere Namespace where you will provision Tanzu Kubernetes clusters by associating the content library and virtual machine classes with the namespace. See Configure a vSphere Namespace for Tanzu Kubernetes releases.