Creating a Windows MachineSet object on vSphere

You can create a Windows MachineSet object to serve a specific purpose in your OKD cluster on VMware vSphere. For example, you might create infrastructure Windows machine sets and related machines so that you can move supporting Windows workloads to the new Windows machines.

Prerequisites

  • You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).

  • You are using a supported Windows Server as the operating system image with the Docker-formatted container runtime add-on enabled.

Currently, the Docker-formatted container runtime is used in Windows nodes. Kubernetes is deprecating Docker as a container runtime; you can reference the Kubernetes documentation for more information on Docker deprecation. Containerd will be the new supported container runtime for Windows nodes in a future release of Kubernetes.

Machine API overview

The Machine API is a combination of primary resources that are based on the upstream Cluster API project and custom OKD resources.

For OKD 4.7 clusters, the Machine API performs all node host provisioning management actions after the cluster installation finishes. Because of this system, OKD 4.7 offers an elastic, dynamic provisioning method on top of public or private cloud infrastructure.

The two primary resources are:

Machines

A fundamental unit that describes the host for a node. A machine has a providerSpec specification, which describes the types of compute nodes that are offered for different cloud platforms. For example, a machine type for a worker node on Amazon Web Services (AWS) might define a specific machine type and required metadata.

Machine sets

MachineSet resources are groups of machines. Machine sets are to machines as replica sets are to pods. If you need more machines or must scale them down, you change the replicas field on the machine set to meet your compute need.

The following custom resources add more capabilities to your cluster:

Machine autoscaler

The MachineAutoscaler resource automatically scales machines in a cloud. You can set the minimum and maximum scaling boundaries for nodes in a specified machine set, and the machine autoscaler maintains that range of nodes. The MachineAutoscaler object takes effect after a ClusterAutoscaler object exists. Both ClusterAutoscaler and MachineAutoscaler resources are made available by the ClusterAutoscalerOperator object.

Cluster autoscaler

This resource is based on the upstream cluster autoscaler project. In the OKD implementation, it is integrated with the Machine API by extending the machine set API. You can set cluster-wide scaling limits for resources such as cores, nodes, memory, GPU, and so on. You can set the priority so that the cluster prioritizes pods so that new nodes are not brought online for less important pods. You can also set the scaling policy so that you can scale up nodes but not scale them down.

Machine health check

The MachineHealthCheck resource detects when a machine is unhealthy, deletes it, and, on supported platforms, makes a new machine.

In OKD version 3.11, you could not roll out a multi-zone architecture easily because the cluster did not manage machine provisioning. Beginning with OKD version 4.1, this process is easier. Each machine set is scoped to a single zone, so the installation program sends out machine sets across availability zones on your behalf. And then because your compute is dynamic, and in the face of a zone failure, you always have a zone for when you must rebalance your machines. The autoscaler provides best-effort balancing over the life of a cluster.

Preparing your vSphere environment for Windows container workloads

You must prepare your vSphere environment for Windows container workloads by creating the vSphere Windows VM golden image and enabling communication with the internal API server for the WMCO.

Creating the vSphere Windows VM golden image

Create a vSphere Windows virtual machine (VM) golden image.

Prerequisites

  • You have installed a cluster on vSphere configured with hybrid networking using OVN-Kubernetes.

  • You have defined a custom VXLAN port in your hybrid networking configuration to work around the pod-to-pod connectivity issue between hosts.

Procedure

  1. Create the VM from an updated version of the Windows Server 1909 VM image that includes the Microsoft patch KB4565351. This patch is required to set the VXLAN UDP port, which is required for clusters installed on vSphere. This patch is not available for the Windows Server 2019 VM image.

  2. Create the C:\Users\Administrator\.ssh\authorized_keys file in the Windows VM containing the public key that corresponds to the private key that resides in the secret you created in the openshift-windows-machine-config-operator namespace. The private key of the secret was created when first installing the Windows Machine Config Operator (WMCO) to give OKD access to Windows VMs. The authorized_keys file is used to configure SSH in the Windows VM.

  3. Configure SSH on the Windows VM by running the following Powershell script:

    1. # Powershell script to configure SSH on vSphere Windows VMs
    2. Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
    3. $firewallRuleName = "ContainerLogsPort"
    4. $containerLogsPort = "10250"
    5. New-NetFirewallRule -DisplayName $firewallRuleName -Direction Inbound -Action Allow -Protocol TCP -LocalPort $containerLogsPort -EdgeTraversalPolicy Allow
    6. Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    7. Install-Module -Force OpenSSHUtils
    8. Set-Service -Name ssh-agent -StartupType 'Automatic'
    9. Set-Service -Name sshd -StartupType 'Automatic'
    10. Start-Service ssh-agent
    11. Start-Service sshd
    12. $pubKeyConf = (Get-Content -path C:\ProgramData\ssh\sshd_config) -replace '#PubkeyAuthentication yes','PubkeyAuthentication yes'
    13. $pubKeyConf | Set-Content -Path C:\ProgramData\ssh\sshd_config
    14. $passwordConf = (Get-Content -path C:\ProgramData\ssh\sshd_config) -replace '#PasswordAuthentication yes','PasswordAuthentication yes'
    15. $passwordConf | Set-Content -Path C:\ProgramData\ssh\sshd_config
    16. $authFileConf = (Get-Content -path C:\ProgramData\ssh\sshd_config) -replace 'AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys','#AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys'
    17. $authFileConf | Set-Content -Path C:\ProgramData\ssh\sshd_config
    18. $pubKeyLocationConf = (Get-Content -path C:\ProgramData\ssh\sshd_config) -replace 'Match Group administrators','#Match Group administrators'
    19. $pubKeyLocationConf | Set-Content -Path C:\ProgramData\ssh\sshd_config
    20. Restart-Service sshd
    21. New-item -Path $env:USERPROFILE -Name .ssh -ItemType Directory -force

  4. Install and configure VMware Tools version 11.0.6 or greater on the Windows VM. See the VMware Tools documentation for more information.

  5. After installing VMware Tools on the Windows VM, verify the following:

    1. The C:\ProgramData\VMware\VMware Tools\tools.conf file has the following entry:

      1. exclude-nics=

      This entry ensures the following:

      • The cloned vNIC generated on the Windows VM by the hybrid-overlay is not ignored.

      • The VM has an IP address in vCenter.

    2. The VMTools Windows service is running.

  6. Pull all of the required Windows container base images needed for your applications. The images you pull are dependent on the Windows kernel you are using. See Microsoft’s documentation on pulling Windows container base images for more information.

  7. Run the Windows Sysprep tool on the Windows VM:

    1. C:\> sysprep.exe /generalize /oobe /shutdown /unattend:<path_to_unattend.xml>

    An example unattend.xml is provided, which maintains all the changes needed for the WMCO. For example, the unattend.xml file must ensure the Administrator’s home directory stays intact with the SSH public key. You must customize the example to fit your needs.

    Example unattend.xml

    1. <?xml version="1.0" encoding="UTF-8"?>
    2. <!--A sample unattend.xml which helps in setting admin password and running scripts on first boot-->
    3. <unattend xmlns="urn:schemas-microsoft-com:unattend">
    4.    <settings pass="specialize">
    5.       <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http:// www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    6.          <InputLocale>0409:00000409</InputLocale>
    7.          <SystemLocale>en-US</SystemLocale>
    8.          <UILanguage>en-US</UILanguage>
    9.          <UILanguageFallback>en-US</UILanguageFallback>
    10.          <UserLocale>en-US</UserLocale>
    11.       </component>
    12.       <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    13.          <SkipAutoActivation>true</SkipAutoActivation>
    14.       </component>
    15.       <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-SQMApi" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    16.          <CEIPEnabled>0</CEIPEnabled>
    17.       </component>
    18.       <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    19.          <ComputerName>windows-host</ComputerName>
    20.          <ProductKey>My_Product_key</ProductKey>
    21.       </component>
    22.    </settings>
    23.    <settings pass="oobeSystem">
    24.       <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    25.          <AutoLogon>
    26.             <Password>
    27.                <Value>MyPassword</Value>
    28.                <PlainText>true</PlainText>
    29.             </Password>
    30.             <Enabled>true</Enabled>
    31.             <Username>Administrator</Username>
    32.          </AutoLogon>
    33.          <OOBE>
    34.             <HideEULAPage>true</HideEULAPage>
    35.             <HideLocalAccountScreen>true</HideLocalAccountScreen>
    36.             <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    37.             <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    38.             <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    39.             <NetworkLocation>Work</NetworkLocation>
    40.             <ProtectYourPC>1</ProtectYourPC>
    41.             <SkipMachineOOBE>true</SkipMachineOOBE>
    42.             <SkipUserOOBE>true</SkipUserOOBE>
    43.          </OOBE>
    44.          <RegisteredOrganization>Organization</RegisteredOrganization>
    45.          <RegisteredOwner>Owner</RegisteredOwner>
    46.          <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
    47.          <TimeZone>Eastern Standard Time</TimeZone>
    48.          <UserAccounts>
    49.             <AdministratorPassword>
    50.                <Value>MyPassword</Value>
    51.                <PlainText>true</PlainText>
    52.             </AdministratorPassword>
    53.             <LocalAccounts>
    54.                <LocalAccount wcm:action="add">
    55.                   <Description>Administrator</Description>
    56.                   <DisplayName>Administrator</DisplayName>
    57.                   <Group>Administrators</Group>
    58.                   <Name>Administrator</Name>
    59.                </LocalAccount>
    60.             </LocalAccounts>
    61.          </UserAccounts>
    62.       </component>
    63.    </settings>
    64. </unattend>

Enabling communication with the internal API server for the WMCO on vSphere

The Windows Machine Config Operator (WMCO) downloads the Ignition config files from the internal API server endpoint. You must enable communication with the internal API server so that your Windows virtual machine (VM) can download the Ignition config files, and the kubelet on the configured VM can only communicate with the internal API server.

Prerequisites

  • You have installed a cluster on vSphere.

Procedure

  • Add a new DNS entry for api-int.<cluster_name>.<base_domain> that points to the external API server URL api.<cluster_name>.<base_domain>. This can be a CNAME or an additional A record.

The external API endpoint was already created as part of the initial cluster installation on vSphere.

Sample YAML for a Windows MachineSet object on vSphere

This sample YAML defines a Windows MachineSet object running on VMware vSphere that the Windows Machine Config Operator (WMCO) can react upon.

  1. apiVersion: machine.openshift.io/v1beta1
  2. kind: MachineSet
  3. metadata:
  4.   labels:
  5.     machine.openshift.io/cluster-api-cluster: <infrastructure_id> (1)
  6.   name: <windows_machine_set_name> (2)
  7.   namespace: openshift-machine-api
  8. spec:
  9.   replicas: 1
  10.   selector:
  11.     matchLabels:
  12.       machine.openshift.io/cluster-api-cluster: <infrastructure_id> (1)
  13.       machine.openshift.io/cluster-api-machineset: <windows_machine_set_name> (2)
  14.   template:
  15.     metadata:
  16.       labels:
  17.         machine.openshift.io/cluster-api-cluster: <infrastructure_id> (1)
  18.         machine.openshift.io/cluster-api-machine-role: worker
  19.         machine.openshift.io/cluster-api-machine-type: worker
  20.         machine.openshift.io/cluster-api-machineset: <windows_machine_set_name> (2)
  21.         machine.openshift.io/os-id: Windows (3)
  22.     spec:
  23.       metadata:
  24.         labels:
  25.           node-role.kubernetes.io/worker: "" (4)
  26.       providerSpec:
  27.         value:
  28.           apiVersion: vsphereprovider.openshift.io/v1beta1
  29.           credentialsSecret:
  30.             name: vsphere-cloud-credentials
  31.           diskGiB: 128
  32.           kind: VSphereMachineProviderSpec
  33.           memoryMiB: 16384
  34.           network:
  35.             devices:
  36.             - networkName: "<vm_network_name>" (5)
  37.           numCPUs: 4
  38.           numCoresPerSocket: 1
  39.           snapshot: ""
  40.           template: <windows_vm_template_name> (6)
  41.           userDataSecret:
  42.             name: windows-user-data (7)
  43.           workspace:
  44.              datacenter: <vcenter_datacenter_name> (8)
  45.              datastore: <vcenter_datastore_name> (9)
  46.              folder: <vcenter_vm_folder_path> (10)
  47.              resourcePool: <vsphere_resource_pool> (11)
  48.              server: <vcenter_server_ip> (12)
1Specify the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. You can obtain the infrastructure ID by running the following command:
  1. $ oc get -o jsonpath=’{.status.infrastructureName}{“\n”}’ infrastructure cluster
2Specify the Windows machine set name. The machine set name cannot be more than 9 characters long, due to the way machine names are generated in vSphere.
3Configure the machine set as a Windows machine.
4Configure the Windows node as a compute machine.
5Specify the vSphere VM network to deploy the machine set to.
6Specify the full path of the Windows vSphere VM template to use, such as /Datacenter/vm/ocp4-llplx/windows-golden-image. The name must be unique.

Do not specify the original VM template. The VM template must remain off and must be cloned for new FCOS machines. Starting the VM template configures the VM template as a VM on the platform, which prevents it from being used as a template that machine sets can apply configurations to.

7The windows-user-data is created by the WMCO when the first Windows machine is configured. After that, the windows-user-data is available for all subsequent machine sets to consume.
8Specify the vCenter Datacenter to deploy the machine set on.
9Specify the vCenter Datastore to deploy the machine set on.
10Specify the path to the vSphere VM folder in vCenter, such as /dc1/vm/user-inst-5ddjd.
11Optional: Specify the vSphere resource pool for your Windows VMs.
12Specify the vCenter server IP or fully qualified domain name.

Creating a machine set

In addition to the ones created by the installation program, you can create your own machine sets to dynamically manage the machine compute resources for specific workloads of your choice.

Prerequisites

  • Deploy an OKD cluster.

  • Install the OpenShift CLI (oc).

  • Log in to oc as a user with cluster-admin permission.

Procedure

  1. Create a new YAML file that contains the machine set custom resource (CR) sample and is named <file_name>.yaml.

    Ensure that you set the <clusterID> and <role> parameter values.

    1. If you are not sure which value to set for a specific field, you can check an existing machine set from your cluster:

      1. $ oc get machinesets -n openshift-machine-api

      Example output

      1. NAME                                DESIRED   CURRENT   READY   AVAILABLE   AGE
      2. agl030519-vplxk-worker-us-east-1a   1         1         1       1           55m
      3. agl030519-vplxk-worker-us-east-1b   1         1         1       1           55m
      4. agl030519-vplxk-worker-us-east-1c   1         1         1       1           55m
      5. agl030519-vplxk-worker-us-east-1d   0         0                             55m
      6. agl030519-vplxk-worker-us-east-1e   0         0                             55m
      7. agl030519-vplxk-worker-us-east-1f   0         0                             55m

    2. Check values of a specific machine set:

      1. $ oc get machineset <machineset_name> -n \
      2.      openshift-machine-api -o yaml

      Example output

      1. ...
      2. template:
      3.     metadata:
      4.       labels:
      5.         machine.openshift.io/cluster-api-cluster: agl030519-vplxk (1)
      6.         machine.openshift.io/cluster-api-machine-role: worker (2)
      7.         machine.openshift.io/cluster-api-machine-type: worker
      8.         machine.openshift.io/cluster-api-machineset: agl030519-vplxk-worker-us-east-1a
      1The cluster ID.
      2A default node label.

  2. Create the new MachineSet CR:

    1. $ oc create -f <file_name>.yaml

  3. View the list of machine sets:

    1. $ oc get machineset -n openshift-machine-api

    Example output

    1. NAME                                      DESIRED   CURRENT   READY   AVAILABLE   AGE
    2. agl030519-vplxk-windows-worker-us-east-1a    1         1         1       1        11m
    3. agl030519-vplxk-worker-us-east-1a            1         1         1       1        55m
    4. agl030519-vplxk-worker-us-east-1b            1         1         1       1        55m
    5. agl030519-vplxk-worker-us-east-1c            1         1         1       1        55m
    6. agl030519-vplxk-worker-us-east-1d            0         0                          55m
    7. agl030519-vplxk-worker-us-east-1e            0         0                          55m
    8. agl030519-vplxk-worker-us-east-1f            0         0                          55m

    When the new machine set is available, the DESIRED and CURRENT values match. If the machine set is not available, wait a few minutes and run the command again.

Additional resources

  • For more information on managing machine sets, see the Machine management section.