Vcenter Namespaces Instances VpcNetworkSetSpec

The Vcenter Namespaces Instances VpcNetworkSetSpec schema contains specifications to set on an existing VPC Namespace Network configuration.

This schema was added in vSphere API 9.0.0.0.

JSON Example

{
    "default_subnet_size": 0,
    "shared_subnets": [
        {
            "path": "string"
        }
    ],
    "private_cidrs": [
        {
            "address": "string",
            "prefix": 0
        }
    ]
}

integer As int64 As int64

default_subnet_size

Optional

Default size of vSphere Namespace Subnets. Changing the default will only affect new Subnets being created.

This property was added in vSphere API 9.0.0.0.

If missing or null, a default Subnet size of /27 (or 32 addresses) is set.

array of Vcenter Namespaces Instances SharedSubnet

shared_subnets

Optional

Subnets created outside of the Supervisor to be associated with this vSphere Namespace.

You can associate more Subnets created outside of the Supervisor with this vSphere Namespace or unassociate some Subnets from this vSphere Namespace as long as the Subnets are not already used in this vSphere Namespace. When setting a vSphere Namespace with that already have Subnets associated, you need to provide a complete list of existing Subnets. Subnets currently associated to a vSphere Namespace that are not provided in this spec will be removed. Unassociating a shared Subnet that is still in use will result in a Vapi Std Errors NotAllowedInCurrentState error. You can also update the com.vmware.vcenter.namespaces.SharedSubnet#podDefault or com.vmware.vcenter.namespaces.SharedSubnet#vmDefault value from false to true or vice versa.

If all shared Subnets used as Pod or VM default network are unassociated from the vSphere Namespace, Pod or VM default network will use Subnets generated from PrivateTGW IPBlocks or PrivateCIDRs if there is any in Namespace's VPC. Otherwise, Pods or VMs will not be assigned a default network.

This property was added in vSphere API 9.1.0.0.

If missing or null, all Subnets that are currently associated with the namespace will be disassociated from it.

array of Vcenter Namespaces Instances Ipv4Cidr

private_cidrs

Optional

CIDR blocks from which private Subnets are allocated. This range should not overlap with those in Vcenter NamespaceManagement Supervisors Networks Workload VpcNetwork.vpc_connectivity_profile, Vcenter NamespaceManagement Supervisors Networks Workload Network.ip_management, or other services running in the datacenter.

Only appending additional CIDRs is allowed. Modification to existing CIDR ranges will result in the operation failing with a Vapi Std Errors ResourceInUse error. Appending invalid CIDR e.g. overlapping or broadcast or reserved CIDR will result in the operation failing with a Vapi Std Errors InvalidArgument error.

This property was added in vSphere API 9.0.0.0.

If missing or null, the current value will be retained.