From 5c331b74d69d4c999d96c42f157ab872917f5848 Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Fri, 15 Sep 2017 21:14:43 +0800 Subject: [PATCH] Clarify the API to check for device plugins --- docs/concepts/cluster-administration/device-plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cluster-administration/device-plugins.md b/docs/concepts/cluster-administration/device-plugins.md index de3176bd66..ffd13fca89 100644 --- a/docs/concepts/cluster-administration/device-plugins.md +++ b/docs/concepts/cluster-administration/device-plugins.md @@ -31,7 +31,7 @@ A device plugin can register itself with the kubelet through this gRPC service. During the registration, the device plugin needs to send: * The name of its Unix socket. - * The API version against which it was built. + * 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://github.com/kubernetes/kubernetes/pull/48922) as `vendor-domain/resource`.