Ephemeral OS disk placement config so NVMe isn’t always consumed #1247
Description
Tell us about your request
On the v6 Azure VM sizes (e.g. D8ds_v6) Karpenter always places the Ephemeral OS disk on the local NVMe. That eats the entire device, so workloads that relied on the NVMe temp disk suddenly have nothing to mount. Azure already exposes a diffDiskPlacement option (CacheDisk, ResourceDisk, NVMe), but the AKSNodeClass spec doesn’t surface it.
Could you add a field so we can pick Cache/Resource placement when the SKU supports it?
Docs: https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
to use local NVMe for application workloads and not as an ephermal os disk
Are you currently working around this issue?
One option is to set osDiskSize to be bigger than the ephermal disk size, so that a managed disk is provisioned but it comes at a huge cost
Additional Context
No response
Attachments
No response
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment