To support multiple deployment "flavours" (i.e. AKS and bare-metal QEMU on TDX), we need to provide separate node installer deployments, as both deployment scenarios require different components to be installed on the hosts. This prepares this separation, by moving the Microsoft-specific runtime-class-files into the microsoft package set, and including the "flavour" of the deployment in the node installer image name.
msanft
commented
1 week ago
To support multiple deployment "flavours" (i.e. AKS and bare-metal QEMU on TDX), we need to provide separate node installer deployments, as both deployment scenarios require different components to be installed on the hosts. This prepares this separation, by moving the Microsoft-specific runtime-class-files into the
microsoftpackage set, and including the "flavour" of the deployment in the node installer image name.