This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 47%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Hi there,
We received this message from Azure about applying updates to some GPU virtual machines. However the only VMs of this type we are using are either part of an AKS node pool, or are used as compute for a ML workspace endpoint. I'm fairly certain we shouldn't be trying to connect to these machines directly to apply updates as they are supposed to be managed. Is this correct?
Update NVIDIA driver on NVads A10_v5 virtual machines by 31 May 2024
You're receiving this email because you currently use NVads A10 v5 series virtual machnes.
The latest vGPU 17.x driver from NVIDIA is backward compatible only with vGPU 16.x.
To avoid disruptions to your service when we roll out vGPU 17.x, please update the NVIDIA driver in your NVads A10 v5 virtual machines to vGPU 16.x by 31 May 2024.
Thank you. To clarify we have
So for case #1 we are fine but for #2 we will have to upgrade the drivers. Would it be sufficient to upgrade the node pool image?
@Andrew Savory I am not sure if case #2 image upgrade covers the NVIDA update. The documentation from AKS mentions that 18.04 covers GPU images and there are steps mentioned here to check after the upgrade, you might want to try the new image and check if it works. Thanks!!
@Andrew Savory If you are using an online managed endpoint then this should be taken care of by the service, if you are using an AKS online endpoint then node maintenance would be users responsibility. See the differences between online endpoints and AKS endpoints.
For upgrading the drivers, please see this page.