From d323e21dc40559c473a628e6f03e28c0b7837ff6 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Fri, 23 Sep 2022 18:58:55 +0100 Subject: [PATCH] Label vendor-specific content as thirdparty --- content/en/docs/tasks/manage-gpus/scheduling-gpus.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/tasks/manage-gpus/scheduling-gpus.md b/content/en/docs/tasks/manage-gpus/scheduling-gpus.md index 4f1857138e..9eb70a9003 100644 --- a/content/en/docs/tasks/manage-gpus/scheduling-gpus.md +++ b/content/en/docs/tasks/manage-gpus/scheduling-gpus.md @@ -23,6 +23,8 @@ some of the limitations in the implementation. Kubernetes implements {{< glossary_tooltip text="device plugins" term_id="device-plugin" >}} to let Pods access specialized hardware features such as GPUs. +{{% thirdparty-content %}} + As an administrator, you have to install GPU drivers from the corresponding hardware vendor on the nodes and run the corresponding device plugin from the GPU vendor. Here are some links to vendors' instructions: