The Edge Compute Stack service uses a configuration file to provide configuration for the Edge Compute Stack hosts, this file will describe the disired state of the configuration for each of the Edge hosts.

As part of the configuration files, the VMware Edge Compute Stack service uses a Kubernetes custom resources exposing Edge Compute Stack Host configuration. This provides a unified devops user interface experience for all configuration at an Edge location.

The configuration file is placed in your Git repository with a name chosen by you ending in .yaml (for example, hostconfig.yaml). This file is used to configure the Edge Compute Stack host after synchronization.

The following example shows a HostConfiguration object to set NTP configuration for an Edge Compute Stack host. For more advanced host configuration examples, visit the Example repository https://github.com/alanrenouf/ECSExample.

apiVersion: esx.vmware.com/v1alpha1
kind: HostConfiguration
metadata:
  name: ec-host-config
  namespace: esx-system
spec:
  layertype: Incremental
  profile: |
    {
      "esx": {
        "system": {
          "system_time": {
            "enabled": true,
            "protocol": "NTP",
            "ntp_config": {
              "server": [{
                  "hostname": "0.pool.ntp.org",
                  "command": "SERVER"
                },
                {
                  "hostname": "1.pool.ntp.org",
                  "command": "SERVER"
                }
              ]
            }
          }
        }
      }
    }

Applying Configuration

Configuration is applied to the Edge Compute Stack host depending on what configuration is changed. If the change requires a reboot, immediate host reboot is initiated. If the change requires entering the maintenance mode, the host automatically enters the maintenance mode.

After the configuration is applied, the Edge Compute Stack host automatically exits the maintenance mode, which causes all previously suspended virtual machine workloads to resume.

Note:

Not all configuration changes require maintenance mode or host reboot (for example, the NTP configuration change shown in the example above). The configuration changes are applied on the running host. In such cases, there is a workload disruption and availability impact. You must plan these updates carefully.