If the TKr content library reaches capacity, you can migrate to a new content library with more storage capacity.

When the vSphere administrator creates a content library, the administrator specifies a datastore for storing library contents, in this case OVA files. Over time as more Kubernetes versions are distributed, the content library will expand in size as OVA files are added for each update. While there is no explicit capacity on the content library, it is limited by its datastore capacity.

If the content library reaches capacity, you might see the message Internal error occurred: get library items failed for. In this case you can migrate TKG clusters to a new content library to increase storage capacity. The migration is done using the vSphere Client.

Procedure

  1. Create a new content library with sufficient capacity for the target cluster.
  2. Log in to the vCenter Server using the vSphere Client.
  3. Select Menu > Hosts and Clusters.
  4. Select the vSphere Cluster object where the Supervisor containing the TKG cluster is provisioned.
  5. Select the Configure tab.
  6. Select the Namespaces > General > option in the navigation panel.
  7. Click Edit beside the Content Library section in the main panel.
  8. Select the new Content Library you created and click OK.
    This action triggers the update to the cluster configuration.
    Note: After you modify the content library, it might take up to 10 minutes for the TKG cluster to pick up the change from the Content Source.