The Instances.UpdateSpec structure contains the specification required to update the configuration on the namespace. This structure is applied partially, and only the specified fields will replace or modify their existing counterparts.


access_list Optional

Access control associated with the namespace. If unset, access controls on the namespace will not be modified. Existing pods from users will continue to run.

description Optional

Description for the namespace. If unset, the description of the namespace will not be modified.

resource_spec Optional

Resource quota updates on the namespace. Refer to com.vmware.vcenter.namespace_management.NamespaceResourceOptions.Info#updateResourceQuotaType 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 ResourceQuotaOptionsV1Update. If unset, the resource constraints on the namespace will not be modified.

storage_specs Optional

Storage associated with the namespace. If unset, storage policies and their limit will not be modified. 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.

vm_service_spec Optional

VM Service specification associated with the namespace. This field is optional because it was added in a newer version than its parent node.

JSON Example

	"access_list": [
			"domain": "string",
			"identity_provider": "string",
			"role": "OWNER",
			"subject": "string",
			"subject_type": "USER"
	"description": "string",
	"resource_spec": {},
	"storage_specs": [
			"limit": 0,
			"policy": "string"
	"vm_service_spec": {
		"content_libraries": [
		"vm_classes": [
Parameter To

Update Instances


Was this page helpful?