Namespaces_Instances_SetSpec
The Instances.SetSpec structure contains the specification required to set a new configuration on the namespace. This structure is applied in entirety, replacing the current specification fully.
{
"description": "string",
"resource_spec": {},
"access_list": [
{
"subject_type": "string",
"subject": "string",
"domain": "string",
"role": "string",
"identity_provider": "string"
}
],
"storage_specs": [
{
"policy": "string",
"limit": 0
}
],
"vm_service_spec": {
"content_libraries": [
"string"
],
"vm_classes": [
"string"
]
},
"content_libraries": [
{
"content_library": "string",
"writable": false
}
]
}
Description for the namespace. If unset, the description of the namespace will be cleared.
Resource quota for the namespace. This will replace the existing resource constraints on the namespace in entirety. Refer to com.vmware.vcenter.namespace_management.NamespaceResourceOptions.Info#createResourceQuotaType and use com.vmware.vcenter.namespace_management.NamespaceResourceOptions#get for retrieving the type for the value for this field. For an example of this, see ResourceQuotaOptionsV1. If unset, the resource constraints on the namespace will be cleared.
Access control associated with the namespace. If unset, the existing access controls on the namespace will be removed and users will not be able to access this namespace to create new pods. Existing pods from users will continue to run.
Storage associated with the namespace. If unset, the existing storage policies will be disassociated with the namespace and existing limits will be cleared. Pods which are already using persistent storage from the earlier version of storage policies will be able to access them till the datastores are attached to the worker nodes.
The Instances.VMServiceSpec structure contains the specification required to configure the VM Service specification associated with a namespace.
List of Content Libraries used by the VM Image Service. This list refers to existing Content Libraries in vSphere inventory. The Content Libraries specified in {VMServiceSpec#contentLibraries} will also be included in this list but will be read-only by default to users.
If the same Content Library is present both here and in {VMServiceSpec#contentLibraries}, then:
- The Content Library is only surfaced to users once.
- The settings here are honored.
If unset, the existing Content Libraries configured for the VM Image Service will be removed.