Enable-WMCluster

Enables the workload management feature on the specified cluster. As a prerequisite, you must establish a connection to a vCenter Server system by using the Connect-VIServer cmdlet. Starting with vSphere 7.0 Update 1, you can use two options for network backing: the NXT-T Container Plugin and the vSphere networking stack. For more information, see Configuring and Managing a Supervisor Cluster (https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-21ABC792-0A23-40EF-8D37-0367B483585E.html)

Syntax

Output

Examples

Example 1

Enable-WMCluster "MyCluster" `
    -SizeHint Tiny `
    -ManagementVirtualNetwork (Get-VirtualNetwork "ManagementNetwork") `
    -ManagementNetworkMode Dhcp `
    -DistributedSwitch "NsxSwitch" `
    -NsxEdgeClusterId "a19ea5ea-3817-4394-83a7-55e4962c90f1" `
    -ServiceCIDR "10.96.0.0/24" `
    -PodCIDRs "10.244.0.0/21" `
    -ExternalIngressCIDRs "10.23.80.0/27" `
    -ExternalEgressCIDRs "10.23.80.0/27" `
    -EphemeralStoragePolicy "MyStoragePolicy1" `
    -ImageStoragePolicy "MyStoragePolicy2" `
    -MasterStoragePolicy "MyStoragePolicy3"

Enables the workload management feature on the "MyCluster" cluster by using the NSX-T Container Plugin. The management interfaces is attached to the network "ManagementNetwork". The management interfaces use Dynamic Host Configuration Protocol (DHCP) to configure its network stack. The vSphere distributed switch "NsxSwitch" provides the overlay networking. You must configure that switch in NSX-T to provide that prior to executing the above example. The NSX edge cluster with ID "a19ea5ea-3817-4394-83a7-55e4962c90f1" provides any higher level network functions that the vCenter system consumes in order to host the workloads.

Example 2

Get-Cluster "MyCluster" | Enable-WMCluster `
    -SizeHint Tiny `
    -ManagementVirtualNetwork (Get-VirtualNetwork "ManagementNetwork") `
    -ManagementNetworkMode StaticRange `
    -ManagementNetworkStartIPAddress "10.23.83.89" `
    -ManagementNetworkAddressRangeSize 5 `
    -ManagementNetworkGateway "10.23.83.253" `
    -ManagementNetworkSubnetMask "255.255.252.0" `
    -OpaqueSwitchName "my-nvds" `
    -NsxEdgeClusterId "a19ea5ea-3817-4394-83a7-55e4962c90f1" `
    -ServiceCIDR "10.96.0.0/24" `
    -PodCIDRs "10.244.0.0/21" `
    -ExternalIngressCIDRs "10.23.87.0/27" `
    -ExternalEgressCIDRs "10.23.88.0/27" `
    -EphemeralStoragePolicy "MyStoragePolicy1" `
    -ImageStoragePolicy "MyStoragePolicy2" `
    -MasterStoragePolicy "MyStoragePolicy3" `
    -ContentLibrary "MyContentLibrary" `
    -WorkerDnsServer "10.23.108.1" `
    -DefaultImageRegistryHostname "myrepository.example.com" `
    -DefaultImageRepository "myrepo" `
    -MasterDnsNames "myk8s.example.com" `
    -MasterDnsServerIPAddress @("10.23.0.1","10.23.0.2") `
    -MasterNtpServer @("10.23.0.3") `
    -MasterDnsSearchDomain "example.com"

Enables the workload management feature on the "MyCluster" cluster by using the NSX-T Container Plugin. The management interfaces are attached to the network "ManagementNetwork". The management interfaces use static network configuration. The NSX-T distributed switch "my-nvds" provides the overlay networking. You must configure that switch in NSX-T in advance to provide that prior to executing the above example. The NSX edge cluster with ID "a19ea5ea-3817-4394-83a7-55e4962c90f1" provides any higher level network functions that the vCenter system consumes in order to host the workloads.

Example 3

Get-Cluster "MyCluster" | Enable-WMCluster `
   -SizeHint Tiny `
   -ManagementVirtualNetwork (Get-VirtualNetwork "ManagementNetwork" ) `
   -ManagementNetworkMode Dhcp `
   -ManagementNetworkFloatingIPAddress "10.23.78.20" `
   -ServiceCIDR "10.96.0.0/24" `
   -EphemeralStoragePolicy "MyStoragePolicy1" `
   -ImageStoragePolicy "MyStoragePolicy2" `
   -MasterStoragePolicy "MyStoragePolicy3" `
   -ContentLibrary "MyContentLibrary" `
   -HAProxyName "HAProxy1" `
   -HAProxyAddressRanges "192.168.10.50-192.168.10.99" `
   -HAProxyUsername "HAProxy1AdminUser" `
   -HAProxyPassword "pass" `
   -HAProxyDataPlaneAddresses "HAProxy1DataPlane:5556" `
   -HAProxyServerCertificateChain "-----BEGIN CERTIFICATE-----...........-----END CERTIFICATE-----" `
   -PrimaryWorkloadNetworkSpecification ( New-WMNamespaceNetworkSpec `
      -Name "network-1" `
      -Gateway "192.168.10.1" `
      -Subnet "255.255.255.0" `
      -AddressRanges "192.168.10.100-192.168.10.200" `
      -DistributedPortGroup "MyPortgroup" `
   )

Enables the workload management feature on the "MyCluster" cluster by using the vSphere networking stack.

Example 4

$primaryWorkloadNetwork = New-WMNamespaceNetworkSpec `
   -Name "network-1" `
   -Gateway "192.168.10.1" `
   -Subnet "255.255.255.0" `
   -AddressRanges "192.168.10.50-192.168.10.99" `
   -DistributedPortGroup "WM-Management Network"
	
$additionalWorkloadNetwork1 = New-WMNamespaceNetworkSpec `
   -Name "network-1" `
   -Gateway "192.168.10.1" `
   -Subnet "255.255.255.0" `
   -AddressRanges "192.168.10.100-192.168.10.149" `
   -DistributedPortGroup "WM-Management Network"
	
$additionalWorkloadNetwork2 = New-WMNamespaceNetworkSpec `
   -Name "network-1" `
   -Gateway "192.168.10.1" `
   -Subnet "255.255.255.0" `
   -AddressRanges "192.168.10.50-192.168.150.200" `
   -DistributedPortGroup "WM-Management Network"

Get-Cluster "MyCluster" | Enable-WMCluster `
   -SizeHint Tiny `
   -ManagementVirtualNetwork (Get-VirtualNetwork "ManagementNetwork" ) `
   -ManagementNetworkMode Dhcp `
   -ManagementNetworkFloatingIPAddress "10.23.78.20" `
   -ServiceCIDR "10.96.0.0/24" `
   -EphemeralStoragePolicy "MyStoragePolicy1" `
   -ImageStoragePolicy "MyStoragePolicy2" `
   -MasterStoragePolicy "MyStoragePolicy3" `
   -ContentLibrary "MyContentLibrary" `
   -HAProxyName "HAProxy1" `
   -HAProxyAddressRanges "192.168.10.50-192.168.10.99" `
   -HAProxyUsername "HAProxy1AdminUser" `
   -HAProxyPassword "pass" `
   -HAProxyDataPlaneAddresses "HAProxy1DataPlane:5556" `
   -HAProxyServerCertificateChain "-----BEGIN CERTIFICATE-----...........-----END CERTIFICATE-----" `
   -PrimaryWorkloadNetworkSpecification $primaryWorkloadNetwork `
   -AdditionalWorkloadNetworkSpecifications $additionalWorkloadNetwork1, $additionalWorkloadNetwork2

Enables the workload management feature on the "MyCluster" cluster by using the vSphere networking stack. First, use the New-WMNamespaceNetworkSpec cmdlet to create specifications for the namespace networks. Second, use the Enable-WMCluster cmdlet to create the specified namespace networks - one primary and two additional ones - which can later be utilized by the workloads.

Related Commands

WMCluster

This cmdlet deactivates the workload management feature on the specified cluster.

Enables the workload management feature on the specified cluster.

This cmdlet retrieves the configuration for the workload management feature of the clusters in the vCenter Server system.

This cmdlet modifies the workload settings of a Tanzu Kubernetes Grid cluster.