@@ -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.1 /nvidia-device-plugin.yml
85
+ $ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.7.0-rc.2 /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.1 `) includes
126
+ The `helm` chart for the latest release of the plugin (`v0.7.0-rc.2 `) includes
127
127
a number of customizable values. The most commonly overridden ones are :
128
128
129
129
` ` `
@@ -161,7 +161,7 @@ that you can set in your pod spec to get access to a specific MIG device.
161
161
Please take a look in the following `values.yaml` file to see the full set of
162
162
overridable parameters for the device plugin.
163
163
164
- * https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.0-rc.1 /deployments/helm/nvidia-device-plugin/values.yaml
164
+ * https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.0-rc.2 /deployments/helm/nvidia-device-plugin/values.yaml
165
165
166
166
# ### Installing via `helm install`from the `nvidia-device-plugin` `helm` repository
167
167
@@ -184,7 +184,7 @@ plugin with the various flags from above.
184
184
Using the default values for the flags :
185
185
` ` ` shell
186
186
$ helm install \
187
- --version=0.7.0-rc.1 \
187
+ --version=0.7.0-rc.2 \
188
188
--generate-name \
189
189
nvdp/nvidia-device-plugin
190
190
` ` `
@@ -193,7 +193,7 @@ Enabling compatibility with the `CPUManager` and running with a request for
193
193
100ms of CPU time and a limit of 512MB of memory.
194
194
` ` ` shell
195
195
$ helm install \
196
- --version=0.7.0-rc.1 \
196
+ --version=0.7.0-rc.2 \
197
197
--generate-name \
198
198
--set compatWithCPUManager=true \
199
199
--set resources.requests.cpu=100m \
@@ -204,7 +204,7 @@ $ helm install \
204
204
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`) :
205
205
` ` ` shell
206
206
$ helm install \
207
- --version=0.7.0-rc.1 \
207
+ --version=0.7.0-rc.2 \
208
208
--generate-name \
209
209
--set legacyDaemonsetAPI=true \
210
210
nvdp/nvidia-device-plugin
@@ -213,7 +213,7 @@ $ helm install \
213
213
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
214
214
` ` ` shell
215
215
$ helm install \
216
- --version=0.7.0-rc.1 \
216
+ --version=0.7.0-rc.2 \
217
217
--generate-name \
218
218
--set compatWithCPUManager=true \
219
219
--set migStrategy=mixed \
@@ -231,7 +231,7 @@ Using the default values for the flags:
231
231
` ` ` shell
232
232
$ helm install \
233
233
--generate-name \
234
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.1 .tgz
234
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.2 .tgz
235
235
` ` `
236
236
237
237
Enabling compatibility with the `CPUManager` and running with a request for
@@ -242,15 +242,15 @@ $ helm install \
242
242
--set compatWithCPUManager=true \
243
243
--set resources.requests.cpu=100m \
244
244
--set resources.limits.memory=512Mi \
245
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.1 .tgz
245
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.2 .tgz
246
246
` ` `
247
247
248
248
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`) :
249
249
` ` ` shell
250
250
$ helm install \
251
251
--generate-name \
252
252
--set legacyDaemonsetAPI=true \
253
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.1 .tgz
253
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.2 .tgz
254
254
` ` `
255
255
256
256
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
@@ -259,31 +259,31 @@ $ helm install \
259
259
--generate-name \
260
260
--set compatWithCPUManager=true \
261
261
--set migStrategy=mixed \
262
- https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.1 .tgz
262
+ https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.0-rc.2 .tgz
263
263
` ` `
264
264
265
265
# # Building and Running Locally
266
266
267
267
The next sections are focused on building the device plugin locally and running it.
268
268
It is intended purely for development and testing, and not required by most users.
269
- It assumes you are pinning to the latest release tag (i.e. `v0.7.0-rc.1 `), but can
269
+ It assumes you are pinning to the latest release tag (i.e. `v0.7.0-rc.2 `), but can
270
270
easily be modified to work with any available tag or branch.
271
271
272
272
# ## With Docker
273
273
274
274
# ### Build
275
275
Option 1, pull the prebuilt image from [Docker Hub](https://hub.docker.com/r/nvidia/k8s-device-plugin) :
276
276
` ` ` shell
277
- $ docker pull nvidia/k8s-device-plugin:v0.7.0-rc.1
278
- $ docker tag nvidia/k8s-device-plugin:v0.7.0-rc.1 nvidia/k8s-device-plugin:devel
277
+ $ docker pull nvidia/k8s-device-plugin:v0.7.0-rc.2
278
+ $ docker tag nvidia/k8s-device-plugin:v0.7.0-rc.2 nvidia/k8s-device-plugin:devel
279
279
` ` `
280
280
281
281
Option 2, build without cloning the repository :
282
282
` ` ` shell
283
283
$ docker build \
284
284
-t nvidia/k8s-device-plugin:devel \
285
285
-f docker/amd64/Dockerfile.ubuntu16.04 \
286
- https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.0-rc.1
286
+ https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.0-rc.2
287
287
` ` `
288
288
289
289
Option 3, if you want to modify the code :
@@ -337,6 +337,13 @@ $ ./k8s-device-plugin --pass-device-specs
337
337
338
338
# # Changelog
339
339
340
+ # ## Version v0.7.0-rc.2
341
+
342
+ - Add the ability to set 'resources' as part of a helm install
343
+ - Add overrides for name and fullname in helm chart
344
+ - Add ability to override image related parameters helm chart
345
+ - Add conditional support for overriding secutiryContext in helm chart
346
+
340
347
# ## Version v0.7.0-rc.1
341
348
342
349
- Added `migStrategy` as a parameter to select the MIG strategy to the helm chart
0 commit comments