From 9034e1b2b401e4175fb2680bb58f40695bfeb654 Mon Sep 17 00:00:00 2001 From: lovejoy Date: Thu, 21 Jun 2018 15:35:09 +0800 Subject: [PATCH] fix-direct-link (#9179) --- .../extend-kubernetes/compute-storage-net/device-plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md index 637c32f11f..f9e5d88bb7 100644 --- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md +++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md @@ -37,7 +37,7 @@ During the registration, the device plugin needs to send: * The name of its Unix socket. * The Device Plugin API version against which it was built. * The `ResourceName` it wants to advertise. Here `ResourceName` needs to follow the - [extended resource naming scheme](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#extended-resources) + [extended resource naming scheme](/docs/concepts/configuration/manage-compute-resources-container/#extended-resources) as `vendor-domain/resource`. For example, an Nvidia GPU is advertised as `nvidia.com/gpu`.