Azure
[Feature] Custom Node (OS) image for AKS cluster nodes
Describe the solution you'd like Allow users to use custom OS image version for AKS cluster nodes, similar to Amazon's custom Amazon Linux AMIs for Amazon EKS
Add a user story here: A team need to use spot GPU nodes for burst jobs, but the jobs come in intermittently. Currently, lack of GPU node image (for now, GPU driver needed to be auto installed after the node being deployed) cause the slow startup. If not considering allocation time, it will take 5 minutes for node to be started (and containered being started). This is harmful for FinOps consideration. Based on syslog, auto GPU driver installation will take around 1 min. And if that time can be cut, this will be good.
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs within 7 days of this comment. @allyford, @stl327
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
we are using aks managed cluster, as of today is the custom / hardened image feature for aks nodepools is available ? This feature is there in OKE ( oracle ), EKS (amazon)
AKS does not support custom node images and we don't have any plans to add support for this feature. We are actively working on a feature call Node Customization which will allow for caching container images. We also have Artifact Streaming as an option for customers looking for reductions in pod start up time. https://learn.microsoft.com/azure/aks/artifact-streaming cc @stl327
@allyford could you link up the issue for Node Customization? Also what about the other valid use cases that a custom node would have unlocked? E.g. customizing the kubelet config via a drop in, or building a raid volume from local NVMe drives to back kubelet.
