Namespaces_Instances_NsxNetworkCreateSpec

Namespaces_Instances_NsxNetworkCreateSpec
Namespaces_Instances_NsxNetworkCreateSpec

The Instances.NsxNetworkCreateSpec structure describes the configuration specification of a NSXT-backed Namespaces Network configuration.

JSON Example
{
    "namespace_network_cidrs": [
        {
            "address": "string",
            "prefix": 0
        }
    ],
    "ingress_cidrs": [
        {
            "address": "string",
            "prefix": 0
        }
    ],
    "egress_cidrs": [
        {
            "address": "string",
            "prefix": 0
        }
    ],
    "nsx_tier0_gateway": "string",
    "subnet_prefix_length": 0,
    "routed_mode": false,
    "load_balancer_size": "string"
}
namespace_network_cidrs
Optional

CIDR blocks from which Kubernetes allocates IP addresss for all workloads that attach to the namespace, including PodVMs, TKGS and VM Service VMs. This range should not overlap with those in Instances.NsxNetworkCreateSpec.ingress-cidrs, Instances.NsxNetworkCreateSpec.egress-cidrs, or other services running in the datacenter. This field is required when Instances.NsxNetworkCreateSpec.nsx-tier0-gateway or any of Instances.NsxNetworkCreateSpec.ingress-cidrs, Instances.NsxNetworkCreateSpec.egress-cidrs are specified. An update operation only allows for addition of new CIDR blocks to the existing list.

ingress_cidrs
Optional

CIDR blocks from which NSX assigns IP addresses for Kubernetes Ingresses and Kubernetes Services of type LoadBalancer. These ranges should not overlap with those in Instances.NsxNetworkCreateSpec.namespace-network-cidrs, Instances.NsxNetworkCreateSpec.egress-cidrs, or other services running in the datacenter. This field is required when Instances.NsxNetworkCreateSpec.nsx-tier0-gateway or any of Instances.NsxNetworkCreateSpec.namespace-network-cidrs, Instances.NsxNetworkCreateSpec.egress-cidrs are specified. An update operation only allows for addition of new CIDR blocks to the existing list.

egress_cidrs
Optional

CIDR blocks from which NSX assigns IP addresses used for performing SNAT from container IPs to external IPs. These ranges should not overlap with those in Instances.NsxNetworkCreateSpec.namespace-network-cidrs, Instances.NsxNetworkCreateSpec.ingress-cidrs, or other services running in the datacenter. This field is required when Instances.NsxNetworkCreateSpec.routed-mode is set to False and Instances.NsxNetworkCreateSpec.nsx-tier0-gateway or any of Instances.NsxNetworkCreateSpec.namespace-network-cidrs, Instances.NsxNetworkCreateSpec.ingress-cidrs is specified. When Instances.NsxNetworkCreateSpec.routed-mode is set to True, this field is not allowed. An update operation only allows for addition of new CIDR blocks to the existing list.

string
nsx_tier0_gateway
Optional

NSX Tier0 Gateway used for this namespace. This field does not allow update once applied. If unset, cluster level settings specified in com.vmware.vcenter.namespace_management.Clusters.NCPClusterNetworkInfo#nsxTier0Gateway will be applied. When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: NSXTier0Gateway. When operations return a value of this structure as a result, the field will be an identifier for the resource type: NSXTier0Gateway.

integer As int64
subnet_prefix_length
Optional

Size of the subnet reserved for namespace segments. If unset, cluster level settings specified in com.vmware.vcenter.namespace_management.Clusters.NCPClusterNetworkInfo#namespaceSubnetPrefix will be applied.

boolean
routed_mode
Optional

Routed mode for this namespace. When set to True, the traffic in the namespace is not NATed. If unset, defaults to False. When this field is set to True, Instances.NsxNetworkCreateSpec.egress-cidrs is not allowed. This field does not allow update once applied.

load_balancer_size
Optional

The Instances.LoadBalancerSize enumerates the kinds of load balancer sizes supported by NSX. Small load balancer can host 10 to 20 virtual servers depending on NSX-T version. Medium load balancer can host 100 virtual servers. Large load balancer can host 1000 virtual servers.
SMALL : Load balancer size of 'small'.
MEDIUM : Load balancer size of 'medium'.
LARGE : Load balancer size of 'large'.