This section describes the Machine resource used in Mirantis Container Cloud API. The Machine resource describes the machine-level parameters.

For demonstration purposes, the Container Cloud the Machine custom resource (CR) can be split into the following major sections:


The fields in this resource are available for viewing only. They are automatically generated by the vSphere cloud provider and must not be modified using Container Cloud API.


The Container Cloud Machine custom resource (CR) contains the following fields:

  • apiVersion

  • kind

    Object type that is Machine

The metadata object field of the Machine resource contains the following fields:

  • name

    Name of the Machine object

  • namespace

    Container Cloud project in which the machine has been created

  • labels


      Provider type that is vsphere for vSphere machines and matches the provider type in the Cluster object


      Region name that matches the region name in the Cluster object


      Cluster name that the machine is assigned to


      • For the control plane role of a machine, this label contains any value, for example, "true"

      • For the worker role, this label is absent or does not contain any value

Configuration example:

kind: Machine
  name: example-control-plane
  namespace: example-ns
  labels: vsphere region-one example-cluster "true" # remove for worker

spec:providerSpec for instance configuration

The spec object field of the Machine object represents the VsphereMachineProviderSpec subresource with all required details to create a vSphere virtual machine. It contains the following fields:

  • apiVersion

  • kind


  • machineRef

    Field used to look up a vSphere VM. The field value is set automatically at runtime by the vSphere provider and must not be set or modified manually.

  • network

    Network configuration of a vSphere VM:

    • devices

      List of network devices connected to a vSphere virtual machine. This list is managed by the vSphere provider depending on static or dynamic network configuration. For details on network objects, see VMware vSphere network objects and IPAM recommendations.

    • diskGiB

      Disk size of a VM.

    • memoryMiB

      RAM size of a VM.

    • numCPUs

      CPU number of a VM.

    • rhelLicense

      For RHEL-based deployments, a RHEL license name to be applied to a vSphere VM.

    • template

      Full path to an OVF template used to create a VM.

    • nodeLabels

      List of node labels to be attached to a node for the user to run certain components on separate cluster nodes. The list of allowed node labels is located in the Cluster object status providerStatus.releaseRef.current.allowedNodeLabels field.

      Starting from Container Cloud 2.17.0, if the value field is not defined in allowedNodeLabels, a label can have any value.

      Before or after a machine deployment, add the required label from the allowed node labels list with the corresponding value to spec.providerSpec.value.nodeLabels in machine.yaml. For example:

      - key: stacklight
        value: enabled

      The addition of a node label that is not available in the list of allowed node labels is restricted.

  • maintenance

    Maintenance mode of a machine. If enabled, the node of the selected machine is drained, cordoned, and prepared for maintenance operations.

Configuration example:

    diskGiB: 120
    kind: VsphereMachineProviderSpec
    memoryMiB: 24576
      creationTimestamp: null
      - dhcp4: true
    numCPUs: 8
    rhelLicense: rhel-license
    template: /DATACENTER/vm/vm-folder/templates/rhel-7.9-template


The status object field of the vSphere Machine object represents the VsphereMachineProviderStatus subresource that describes the current state of a vSphere virtual machine. It contains the following fields:

  • apiVersion

  • kind


  • conditions

    List of a machine status conditions:

    • type

      Object type, for example, Kubelet

    • ready

      Readiness flag

    • message

      Status details

  • providerInstanceState

    Current state of a vSphere VM:

    • id

      ID of a VM

    • ready

      Readiness flag

    • state

      State of a VM

  • networkStatus

    Network status of a vSphere VM:

    • networkName

      vSphere network name that a VM is assigned to

    • connected

      Flag indicating whether the network is currently connected to the VM

    • ipAddrs

      One or more IP addresses reported by vm-tools

    • macAddr

      MAC addresses of the VM network interface

  • privateIp

    Private IPv4 address assigned to a VM

  • maintenance

    Maintenance mode of a machine. If enabled, the node of the selected machine is drained, cordoned, and prepared for maintenance operations.

  • status

    Current status of a machine:

    • Provision

      A machine is yet to obtain a status

    • Uninitialized

      A machine is yet to obtain the node IP address and host name

    • Pending

      A machine is yet to receive the deployment instructions and it is either not booted yet or waits for the LCM controller to be deployed

    • Prepare

      A machine is running the Prepare phase during which Docker images and packages are being predownloaded

    • Deploy

      A machine is processing the LCM Controller instructions

    • Reconfigure

      A machine is being updated with a configuration without affecting workloads running on the machine

    • Ready

      A machine is deployed and the supported Mirantis Kubernetes Engine (MKE) version is set

    • Maintenance

      A machine host is cordoned, drained, and prepared for maintenance operations

Configuration example:

    - message: Kubelet's NodeReady condition is True
      ready: true
      type: Kubelet
    - message: Swarm state of the machine is ready
      ready: true
      type: Swarm
    - message: Maintenance state of the machine is false
      ready: true
      type: Maintenance
    - message: LCM Status of the machine is Ready
      ready: true
      type: LCM
    - message: Provider instance 4215081f-7460-be62-0274-e437f6a1fe9b has status green
      ready: true
      type: ProviderInstance
    hardware: {}
    kind: VsphereMachineProviderStatus
      creationTimestamp: null
    - connected: true
      macAddr: 00:50:56:95:54:a0
      networkName: VMWare_Network
      id: 4215081f-7460-be62-0274-e437f6a1fe9b
      ready: true
      state: green
    ready: true
    status: Ready
    upgradeIndex: 3