From 6b208f8acf4c0286e48fbeb05d08588a813d98b9 Mon Sep 17 00:00:00 2001 From: Ed Bartosh Date: Tue, 12 Jan 2021 12:42:22 +0200 Subject: [PATCH] documentation: remove kubelet configuration check Removed device plugin socket check from the documentation as device plugin support is enabled by default in Kubelet. Signed-off-by: Ed Bartosh --- cmd/dsa_plugin/README.md | 11 ----------- cmd/fpga_plugin/README.md | 13 +------------ cmd/gpu_plugin/README.md | 13 +------------ cmd/qat_plugin/README.md | 13 +------------ cmd/sgx_plugin/README.md | 11 ----------- cmd/vpu_plugin/README.md | 13 +------------ 6 files changed, 4 insertions(+), 70 deletions(-) diff --git a/cmd/dsa_plugin/README.md b/cmd/dsa_plugin/README.md index acfb9f9f..0c59eed0 100644 --- a/cmd/dsa_plugin/README.md +++ b/cmd/dsa_plugin/README.md @@ -54,17 +54,6 @@ $ export INTEL_DEVICE_PLUGINS_SRC=/path/to/intel-device-plugins-for-kubernetes $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes ${INTEL_DEVICE_PLUGINS_SRC} ``` -### Verify node kubelet config - -Every node that will be running the dsa plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet To deploy the dsa plugin as a daemonset, you first need to build a container image for the diff --git a/cmd/fpga_plugin/README.md b/cmd/fpga_plugin/README.md index a24db0da..b53a4aa7 100644 --- a/cmd/fpga_plugin/README.md +++ b/cmd/fpga_plugin/README.md @@ -163,17 +163,6 @@ $ export INTEL_DEVICE_PLUGINS_SRC=/path/to/intel-device-plugins-for-kubernetes $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes ${INTEL_DEVICE_PLUGINS_SRC} ``` -### Verify node kubelet config - -Every node that will be running the FPGA plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet As a pre-requisite you need to have [cert-manager](https://cert-manager.io) @@ -337,4 +326,4 @@ $ sudo -E ${INTEL_DEVICE_PLUGINS_SRC}/cmd/fpga_plugin/fpga_plugin -mode region - FPGA device plugin started in region mode device-plugin start server at: /var/lib/kubelet/device-plugins/fpga.intel.com-region-ce48969398f05f33946d560708be108a.sock device-plugin registered -``` \ No newline at end of file +``` diff --git a/cmd/gpu_plugin/README.md b/cmd/gpu_plugin/README.md index f0b775c8..f52a6aae 100644 --- a/cmd/gpu_plugin/README.md +++ b/cmd/gpu_plugin/README.md @@ -78,17 +78,6 @@ $ export INTEL_DEVICE_PLUGINS_SRC=/path/to/intel-device-plugins-for-kubernetes $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes ${INTEL_DEVICE_PLUGINS_SRC} ``` -### Verify node kubelet config - -Every node that will be running the gpu plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet To deploy the gpu plugin as a daemonset, you first need to build a container image for the @@ -225,4 +214,4 @@ We can test the plugin is working by deploying the provided example OpenCL image Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling default-scheduler 0/1 nodes are available: 1 Insufficient gpu.intel.com/i915. - ``` \ No newline at end of file + ``` diff --git a/cmd/qat_plugin/README.md b/cmd/qat_plugin/README.md index 85759288..dc7339ce 100644 --- a/cmd/qat_plugin/README.md +++ b/cmd/qat_plugin/README.md @@ -147,17 +147,6 @@ $ export INTEL_DEVICE_PLUGINS_SRC=/path/to/intel-device-plugins-for-kubernetes $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes ${INTEL_DEVICE_PLUGINS_SRC} ``` -### Verify node kubelet config - -Every node that will be running the plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet To deploy the plugin as a DaemonSet, you first need to build a container image for the plugin and @@ -362,4 +351,4 @@ for i in 0442 0443 37c9 19e3; do lspci -d 8086:$i; done [6]:https://github.com/kata-containers/documentation/blob/master/use-cases/using-Intel-QAT-and-kata.md [7]:https://01.org/sites/default/files/downloads//336210-009qatswprogrammersguide.pdfhttps://01.org/sites/default/files/downloads//336210-009qatswprogrammersguide.pdf [8]:https://github.com/kata-containers/documentation/blob/master/use-cases/using-Intel-QAT-and-kata.md#build-openssl-intel-qat-engine-container -[9]:https://01.org/sites/default/files/downloads/intelr-quickassist-technology/336212qatswgettingstartedguiderev003.pdf \ No newline at end of file +[9]:https://01.org/sites/default/files/downloads/intelr-quickassist-technology/336212qatswgettingstartedguiderev003.pdf diff --git a/cmd/sgx_plugin/README.md b/cmd/sgx_plugin/README.md index 25484a94..f2d87a19 100644 --- a/cmd/sgx_plugin/README.md +++ b/cmd/sgx_plugin/README.md @@ -152,17 +152,6 @@ $ export INTEL_DEVICE_PLUGINS_SRC=/path/to/intel-device-plugins-for-kubernetes $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes ${INTEL_DEVICE_PLUGINS_SRC} ``` -### Verify node kubelet config - -Every node that will be running the plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet To deploy the plugin as a DaemonSet, you first need to build a container image for the plugin and diff --git a/cmd/vpu_plugin/README.md b/cmd/vpu_plugin/README.md index e9c84148..d9fb3409 100644 --- a/cmd/vpu_plugin/README.md +++ b/cmd/vpu_plugin/README.md @@ -54,17 +54,6 @@ $ mkdir -p $(go env GOPATH)/src/github.com/intel $ git clone https://github.com/intel/intel-device-plugins-for-kubernetes $(go env GOPATH)/src/github.com/intel/intel-device-plugins-for-kubernetes ``` -### Verify node kubelet config - -Every node that will be running the vpu plugin must have the -[kubelet device-plugins](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) -configured. For each node, check that the kubelet device plugin socket exists: - -```bash -$ ls /var/lib/kubelet/device-plugins/kubelet.sock -/var/lib/kubelet/device-plugins/kubelet.sock -``` - ### Deploying as a DaemonSet To deploy the vpu plugin as a daemonset, you first need to build a container image for the @@ -251,4 +240,4 @@ Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling default-scheduler 0/1 nodes are available: 1 Insufficient vpu.intel.com/hddl. -``` \ No newline at end of file +```