Intel® Data Center GPU Utilities for VMWare Tanzu* enables installing of Intel® GPU drivers to vanilla Ubuntu Kubernetes nodes. It downloads, builds and loads the kernel driver and corresponding firmware to the node. When the deployment is removed, all the traces of the driver are removed. With the installed GPU driver, node's Intel® GPUs can be utilized to run compute and other GPU accelerated workloads.
CAUTION: This is an alpha / non-production software, do not use on production clusters.
Table of Contents
- Kernel Module Management Operator (KMMO) is instructed by the configuration files to build and deploy Intel GPU Kernel Driver container image to the nodes that have Intel GPU HW and suitable Linux kernel.
- KMMO deploys a Pod to build the GPU kernel driver on one of the GPU enabled nodes.
- Built GPU kernel driver container image is pushed to an external container image registry.
- KMMO deploys Pods via a Daemonset on nodes that have Intel GPU device. The Pod copies FW files and loads the kernel driver into the host kernel.
- Container image including the GPU driver and FW is pulled from the external registry.
- Once the kernel driver is available, Intel GPU plugin starts and registers the GPU resources to the cluster.
The deployment supports a range of Kubernetes cluster versions:
- 1.25 - 1.27
The range comes via the dependency images and their supporter versions:
- Cert-Manager: 1.22 - 1.27
- Node Feature Discovery: 1.21 ->
- Intel Device Plugins: 1.25 - 1.27
While not officially supported or tested, deployment may work fine also on older Kubernetes clusters. The deployment uses basic Kubernetes functionality and its dependencies should not depend on latest Kubernetes features either.
The installation requires a container image registry to be accessible and writable. The registry is used to push and pull the GPU driver container image. The image's URL and the possible authentication details need to be provided to the helm install command, or changed in the values.yaml file.
The driver is installed with a helm chart. This requires helm to be installed.
Install depends on a few variables:
- local.image - Required
- A template URL that will be used to store the GPU driver container image.
- e.g. my.registry.acme.com/intel-gpu-driver
- Resulting container image will have a kernel specific tag: 5.15.0-79-generic
- local.secret.base64 - Recommended
- Secret for accessing the registry, if registry requires authentication.
- Docker's
config.jsonin base64 format.
- build.baseImage - Optional
- If cluster is behind a proxy, set this to an URL that is accessible inside the network.
- e.g. 192.168.0.100/ubuntu:20.04
- proxy - Optional
- http, https, no_proxy
- Used if inside a proxy enabled network. Required to fetch driver code from Github projects during build.
To install the chart:
helm dep update
# values.yaml is updated with gpu driver image URL and credentials
helm install --create-namespace -n inteldeviceplugins intel-gpu .
Registry image URL and credentials can also be given in the helm's install arguments:
helm dep update
helm install --create-namespace -n inteldeviceplugins --set local.image=my.registry.acme.com/intel-gpu-driver --set local.secret.base64=A123424...438483843= intel-gpu .
Once install has succeeded, the Pod listing should look like this:
$ kubectl get pods -n cert-manager
NAME READY STATUS RESTARTS AGE
intel-gpu-cert-manager-7cc59588d6-glvsf 1/1 Running 0 2m7s
intel-gpu-cert-manager-cainjector-8449dfb7db-72fxp 1/1 Running 0 2m7s
intel-gpu-cert-manager-webhook-85f9d8b544-bf2br 1/1 Running 0 2m7s
$ kubectl get pods -n kmm-operator-system
NAME READY STATUS RESTARTS AGE
kmm-i915-backport-build-cz7hl-xnx2w 1/1 Running 0 28s
kmm-operator-controller-manager-9869cb4dd-n2nt4 2/2 Running 0 34s
$ kubectl get pods -n node-feature-discovery
NAME READY STATUS RESTARTS AGE
intel-gpu-nfd-master-f5b8c6c4d-kcmfl 1/1 Running 0 2m29s
intel-gpu-nfd-worker-95nsk 1/1 Running 1 (2m12s ago) 2m29s
intel-gpu-nfd-worker-97d8t 1/1 Running 1 (2m11s ago) 2m30s
Once the kmm-i915-backport-build Pod finishes, the Pods on the kmm-operator-system namespace changes to something like this:
$ kubectl get pods -n kmm-operator-system
NAME READY STATUS RESTARTS AGE
kmm-i915-backport-dfb8318abc717e84-mrxs8 1/1 Running 0 2m10s
kmm-i915-backport-dfb8318abc717e84-nrk5g 1/1 Running 0 2m10s
kmm-operator-controller-manager-9869cb4dd-pfszn 2/2 Running 0 2m21s
After the 'kmm-i915-backport-*' Pod has loaded GPU driver to the node, the Intel GPU plugin will get deployed on the node:
$ kubectl get pods -n inteldeviceplugins
NAME READY STATUS RESTARTS AGE
intel-gpu-plugin-skcdb 1/1 Running 0 2m7s
intel-gpu-plugin-t6hxn 1/1 Running 0 2m7s
inteldeviceplugins-controller-manager-86b94df46c-4wtf6 2/2 Running 0 2m14s
When the gpu.intel.com/i915 resource is registered to nodes, workloads requesting the resource will be scheduled on the nodes.
The chart includes a couple of dependencies that are installed: cert-manager, node-feature-discovery, Intel device plugin operator and GPU device plugin.
In case the target cluster has some of the dependencies already installed. those can be disabled in the values.yaml file, or by setting suitable variables in the install phase.
# disable cert-manager
helm install --create-namespace -n inteldeviceplugins --set deps.certmanager=false intel-gpu .
# disable nfd
helm install --create-namespace -n inteldeviceplugins --set deps.nfd=false intel-gpu .
First check that the issue is not due to known limitations.
The deployment limits in-cluster access to some of the namespaces. If the deployment fails and the symptoms seem like connectivity issues, one can try to disable the network policies in the values.yaml by:
networkpolicy:
enabled: false
In corporate environments proxies are a common thing. One should set the proxies and no_proxies in the values.yaml.
proxy:
http: proxy.acme.com:8080
https: proxy.acme.com:8081
no_proxy: acme.com,localhost,192.168.0.0/24
Sometimes the kernel driver build can fail. Check the build issues from the Pod's logs:
kubectl logs -f -n kmm-operator-system kmm-i915-backport-build-xxxxx-yyyyy
Helm:
helm uninstall -n inteldeviceplugins intel-gpu
Due to how helm handles CRDs, they have to be deleted manually. Cleanup script will also remove any dangling KMM Pods.
bash scripts/cleanup.sh
NOTE: cleanup.sh will remove everything. Modify it to ignore dependencies that you might have installed separately.
When KMMO launches the GPU driver Pod on GPU HW nodes, it copies the firmware files under /var/lib/firmware. This path is not in the default search paths for kernel firmware. Thus, it's best to add firmware_class.path=/var/lib/firmware to the kernel command line.
I915 backport driver supports only a handful of kernel versions. For example Ubuntu 20.04 was released with 5.4 kernel and the supported backport kernel is 5.15. The kernel might need to be updated for the backport driver to compile. The supported OS & kernel versions are listed in the backports project.
- Intel GPU plugin
- Intel Device plugin operator
- Kernel Module Management Operator
- Node Feature Discovery
Project uses Apache 2.0.
Some of the components installed during deployment do use different licenses.