@@ -82,7 +82,7 @@ Once you have configured the options above on all the GPU nodes in your
82
82
cluster, you can enable GPU support by deploying the following Daemonset:
83
83
84
84
``` shell
85
- $ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.7.0-rc.4 /nvidia-device-plugin.yml
85
+ $ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.7.0-rc.5 /nvidia-device-plugin.yml
86
86
```
87
87
88
88
** Note:** This is a simple static daemonset meant to demonstrate the basic
@@ -123,7 +123,7 @@ The preferred method to deploy the device plugin is as a daemonset using `helm`.
123
123
Instructions for installing `helm` can be found
124
124
[here](https://helm.sh/docs/intro/install/).
125
125
126
- The `helm` chart for the latest release of the plugin (`v0.7.0-rc.4 `) includes
126
+ The `helm` chart for the latest release of the plugin (`v0.7.0-rc.5 `) includes
127
127
a number of customizable values. The most commonly overridden ones are :
128
128
129
129
` ` `
@@ -176,7 +176,7 @@ that you can set in your pod spec to get access to a specific MIG device.
176
176
Please take a look in the following `values.yaml` file to see the full set of
177
177
overridable parameters for the device plugin.
178
178
179
- * https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.0-rc.4 /deployments/helm/nvidia-device-plugin/values.yaml
179
+ * https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.0-rc.5 /deployments/helm/nvidia-device-plugin/values.yaml
180
180
181
181
# ### Installing via `helm install`from the `nvidia-device-plugin` `helm` repository
182
182
@@ -199,7 +199,7 @@ plugin with the various flags from above.
199
199
Using the default values for the flags :
200
200
` ` ` shell
201
201
$ helm install \
202
- --version=0.7.0-rc.4 \
202
+ --version=0.7.0-rc.5 \
203
203
--generate-name \
204
204
nvdp/nvidia-device-plugin
205
205
` ` `
@@ -208,7 +208,7 @@ Enabling compatibility with the `CPUManager` and running with a request for
208
208
100ms of CPU time and a limit of 512MB of memory.
209
209
` ` ` shell
210
210
$ helm install \
211
- --version=0.7.0-rc.4 \
211
+ --version=0.7.0-rc.5 \
212
212
--generate-name \
213
213
--set compatWithCPUManager=true \
214
214
--set resources.requests.cpu=100m \
@@ -219,7 +219,7 @@ $ helm install \
219
219
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`) :
220
220
` ` ` shell
221
221
$ helm install \
222
- --version=0.7.0-rc.4 \
222
+ --version=0.7.0-rc.5 \
223
223
--generate-name \
224
224
--set legacyDaemonsetAPI=true \
225
225
nvdp/nvidia-device-plugin
@@ -228,7 +228,7 @@ $ helm install \
228
228
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
229
229
` ` ` shell
230
230
$ helm install \
231
- --version=0.7.0-rc.4 \
231
+ --version=0.7.0-rc.5 \
232
232
--generate-name \
233
233
--set compatWithCPUManager=true \
234
234
--set migStrategy=mixed \
@@ -246,7 +246,7 @@ Using the default values for the flags:
246
246
` ` ` shell
247
247
$ helm install \
248
248
--generate-name \
249
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.4 .tgz
249
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.5 .tgz
250
250
` ` `
251
251
252
252
Enabling compatibility with the `CPUManager` and running with a request for
@@ -257,15 +257,15 @@ $ helm install \
257
257
--set compatWithCPUManager=true \
258
258
--set resources.requests.cpu=100m \
259
259
--set resources.limits.memory=512Mi \
260
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.4 .tgz
260
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.5 .tgz
261
261
` ` `
262
262
263
263
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`) :
264
264
` ` ` shell
265
265
$ helm install \
266
266
--generate-name \
267
267
--set legacyDaemonsetAPI=true \
268
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.4 .tgz
268
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.5 .tgz
269
269
` ` `
270
270
271
271
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
@@ -274,31 +274,31 @@ $ helm install \
274
274
--generate-name \
275
275
--set compatWithCPUManager=true \
276
276
--set migStrategy=mixed \
277
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.4 .tgz
277
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.5 .tgz
278
278
` ` `
279
279
280
280
# # Building and Running Locally
281
281
282
282
The next sections are focused on building the device plugin locally and running it.
283
283
It is intended purely for development and testing, and not required by most users.
284
- It assumes you are pinning to the latest release tag (i.e. `v0.7.0-rc.4 `), but can
284
+ It assumes you are pinning to the latest release tag (i.e. `v0.7.0-rc.5 `), but can
285
285
easily be modified to work with any available tag or branch.
286
286
287
287
# ## With Docker
288
288
289
289
# ### Build
290
290
Option 1, pull the prebuilt image from [Docker Hub](https://hub.docker.com/r/nvidia/k8s-device-plugin) :
291
291
` ` ` shell
292
- $ docker pull nvidia/k8s-device-plugin:v0.7.0-rc.4
293
- $ docker tag nvidia/k8s-device-plugin:v0.7.0-rc.4 nvidia/k8s-device-plugin:devel
292
+ $ docker pull nvidia/k8s-device-plugin:v0.7.0-rc.5
293
+ $ docker tag nvidia/k8s-device-plugin:v0.7.0-rc.5 nvidia/k8s-device-plugin:devel
294
294
` ` `
295
295
296
296
Option 2, build without cloning the repository :
297
297
` ` ` shell
298
298
$ docker build \
299
299
-t nvidia/k8s-device-plugin:devel \
300
300
-f docker/amd64/Dockerfile.ubuntu16.04 \
301
- https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.0-rc.4
301
+ https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.0-rc.5
302
302
` ` `
303
303
304
304
Option 3, if you want to modify the code :
@@ -352,6 +352,10 @@ $ ./k8s-device-plugin --pass-device-specs
352
352
353
353
# # Changelog
354
354
355
+ # ## Version v0.7.0-rc.5
356
+
357
+ - Add deviceListStrategyFlag to allow device list passing as volume mounts
358
+
355
359
# ## Version v0.7.0-rc.4
356
360
357
361
- Allow one to override selector.matchLabels in the helm chart
0 commit comments