NamespaceManagement_Supervisors_ImageSyncConfig
ImageSyncConfig structure describes how the Supervisor Cluster and Kubernetes retrieves VM and container images that will run on the cluster.
{
"registry": {
"hostname": "string",
"port": 0
},
"repository": "string",
"kubernetes_content_library": "string",
"content_libraries": [
{
"content_library": "string"
}
]
}The ImageRegistry structure contains the specification required to configure container image registry endpoint.
The ImageSyncConfig.repository specifies the default container image repository to use when the Kubernetes Pod specification does not specify it. For example, hub.docker.com is the image repository for a Pod whose image specification is hub.docker.com/nginx.
If unset, and if docker hub is the configured ImageSyncConfig.registry, then ImageSyncConfig.repository defaults to Docker Hub. If Docker Hub is not the configured image registry, ImageSyncConfig.repository remains unset. If {#member} repository is unset, you must supply an image repository in your Pod spec or else images will not be able to be synced into the cluster.
ImageSyncConfig.kubernetes-content-library is the UUID of the Content Library which holds the VM Images for Tanzu Kubernetes Service for vSphere.
This Content Library should be subscribed to VMware's hosted vSphere Kubernetes Service Repository. Optionally, you can configure your own local content library and host images locally.
If the Content Library identifier is unset, you will not be able to deploy Tanzu Kubernetes Clusters. When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: com.vmware.content.Library. When operations return a value of this structure as a result, the field will be an identifier for the resource type: com.vmware.content.Library.
ImageSyncConfig.content-libraries is a list of Content Libraries that will be associated with a Supervisor.
This list refers to existing Content Libraries in the vSphere inventory. These Content Libraries and the Content Library items belonging to them will be read-only across all vSphere Namespaces. This list cannot overlap with the defaultKubernetesServiceContentLibrary.
If unset, no additional Content Libraries will be set for the Supervisor apart from the default Kubernetes Service Content Library.