summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com>2017-09-12 07:07:12 -0700
committerGitHub <noreply@github.com>2017-09-12 07:07:12 -0700
commitcab4b92e74392caa74b9e5ecf95708e1b0ed76ea (patch)
treed3d80e4f493a0052ccde0de206d6b61c2f63a8a6
parent95ac59f60d718d3bb1d378a5718a4bb6f9f867bd (diff)
parentbbe6de543356878987e242af831f43e72870b37f (diff)
Merge pull request #1042 from ScorpioCPH/master
Automatic merge from submit-queue Minor fix quick link @RenaudWasTaken @jiayingz PTAL.
-rw-r--r--contributors/design-proposals/device-plugin.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/device-plugin.md b/contributors/design-proposals/device-plugin.md
index 9871ec35..ba2e6905 100644
--- a/contributors/design-proposals/device-plugin.md
+++ b/contributors/design-proposals/device-plugin.md
@@ -198,7 +198,7 @@ When starting the gRPC server, they are expected to create a unix socket
at the following host path: `/var/lib/kubelet/device-plugins/`.
For non bare metal device plugin this means they will have to mount the folder
-as a volume in their pod spec ([see Installation](##installation)).
+as a volume in their pod spec ([see Installation](#installation)).
Device plugins can expect to find the socket to register themselves on
the host at the following path: