You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for Data Disks (VDHX) for Single Machines Cluster that is using local storage by providing a capability to configure one or more datadisks (size, location) in the cluster config so that additional disk are added to the AKS EE Maniner VM and/or AKS EE Windows VM. The rationale is to be able segregate the data from the OS disk and to be able to use different storage classes (tiering).
When the "DataDiskPath" is not provided it should use the INSTALLDIR and VHDXDIR that are used during installation (default, location C:\Program Files\AksEdge)
(optional) - The CBL-Maniner VM could mount and initialize the additional disks with a Physical Volume (pvcreate ) and a new Volume Group should be created (vgcreate). From here the user is then responsible to configure their Storage Provider and classes (similar process would apply on the Windows VM).
The text was updated successfully, but these errors were encountered:
erwinkersten
changed the title
[Feature] Support for additional data disks for Single Machines Cluster
[Feature] Support for additional data disks for Single Machine Cluster
Oct 26, 2023
Feature Request:
Support for Data Disks (VDHX) for Single Machines Cluster that is using local storage by providing a capability to configure one or more datadisks (size, location) in the cluster config so that additional disk are added to the AKS EE Maniner VM and/or AKS EE Windows VM. The rationale is to be able segregate the data from the OS disk and to be able to use different storage classes (tiering).
Example configuration:
When the "DataDiskPath" is not provided it should use the
INSTALLDIR
andVHDXDIR
that are used during installation (default, locationC:\Program Files\AksEdge
)(optional) - The CBL-Maniner VM could mount and initialize the additional disks with a Physical Volume (pvcreate ) and a new Volume Group should be created (vgcreate). From here the user is then responsible to configure their Storage Provider and classes (similar process would apply on the Windows VM).
The text was updated successfully, but these errors were encountered: