Craig Wilhite, rickman_MSFT May I ask a question?
Is it possible to launch such GPU accelerated Windows containers via Kubernetes?
Kubernetes seems to launch containers already in process isolation mode, corresponding to the --isolation process option you are mentioning in the article. But what is the Kubernetes equivalent of the --device class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 option? We see no need for a Kubernetes device plugin, which seems to be the wrong way anyway, since it would assign GPU resources exclusively to a container.
We can successfully run our application in a GPU accelerated Windows container via docker run. We can also create Windows containers via Kubernetes, but without GPU access yet. Optimistically hoping that it is only a small thing we are missing.