Skip to content

Commit 39a47a5

Browse files
committed
Update README.md and RELEASE.md with v0.7.0-rc.5 tag
Signed-off-by: Kevin Klues <[email protected]>
1 parent 3a6af7c commit 39a47a5

File tree

2 files changed

+20
-16
lines changed

2 files changed

+20
-16
lines changed

README.md

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Once you have configured the options above on all the GPU nodes in your
8282
cluster, you can enable GPU support by deploying the following Daemonset:
8383

8484
```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
8686
```
8787

8888
**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`.
123123
Instructions for installing `helm` can be found
124124
[here](https://helm.sh/docs/intro/install/).
125125

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
127127
a number of customizable values. The most commonly overridden ones are:
128128

129129
```
@@ -176,7 +176,7 @@ that you can set in your pod spec to get access to a specific MIG device.
176176
Please take a look in the following `values.yaml` file to see the full set of
177177
overridable parameters for the device plugin.
178178

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
180180

181181
#### Installing via `helm install`from the `nvidia-device-plugin` `helm` repository
182182

@@ -199,7 +199,7 @@ plugin with the various flags from above.
199199
Using the default values for the flags:
200200
```shell
201201
$ helm install \
202-
--version=0.7.0-rc.4 \
202+
--version=0.7.0-rc.5 \
203203
--generate-name \
204204
nvdp/nvidia-device-plugin
205205
```
@@ -208,7 +208,7 @@ Enabling compatibility with the `CPUManager` and running with a request for
208208
100ms of CPU time and a limit of 512MB of memory.
209209
```shell
210210
$ helm install \
211-
--version=0.7.0-rc.4 \
211+
--version=0.7.0-rc.5 \
212212
--generate-name \
213213
--set compatWithCPUManager=true \
214214
--set resources.requests.cpu=100m \
@@ -219,7 +219,7 @@ $ helm install \
219219
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
220220
```shell
221221
$ helm install \
222-
--version=0.7.0-rc.4 \
222+
--version=0.7.0-rc.5 \
223223
--generate-name \
224224
--set legacyDaemonsetAPI=true \
225225
nvdp/nvidia-device-plugin
@@ -228,7 +228,7 @@ $ helm install \
228228
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
229229
```shell
230230
$ helm install \
231-
--version=0.7.0-rc.4 \
231+
--version=0.7.0-rc.5 \
232232
--generate-name \
233233
--set compatWithCPUManager=true \
234234
--set migStrategy=mixed \
@@ -246,7 +246,7 @@ Using the default values for the flags:
246246
```shell
247247
$ helm install \
248248
--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
250250
```
251251

252252
Enabling compatibility with the `CPUManager` and running with a request for
@@ -257,15 +257,15 @@ $ helm install \
257257
--set compatWithCPUManager=true \
258258
--set resources.requests.cpu=100m \
259259
--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
261261
```
262262

263263
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
264264
```shell
265265
$ helm install \
266266
--generate-name \
267267
--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
269269
```
270270

271271
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
@@ -274,31 +274,31 @@ $ helm install \
274274
--generate-name \
275275
--set compatWithCPUManager=true \
276276
--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
278278
```
279279

280280
## Building and Running Locally
281281

282282
The next sections are focused on building the device plugin locally and running it.
283283
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
285285
easily be modified to work with any available tag or branch.
286286

287287
### With Docker
288288

289289
#### Build
290290
Option 1, pull the prebuilt image from [Docker Hub](https://hub.docker.com/r/nvidia/k8s-device-plugin):
291291
```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
294294
```
295295

296296
Option 2, build without cloning the repository:
297297
```shell
298298
$ docker build \
299299
-t nvidia/k8s-device-plugin:devel \
300300
-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
302302
```
303303

304304
Option 3, if you want to modify the code:
@@ -352,6 +352,10 @@ $ ./k8s-device-plugin --pass-device-specs
352352

353353
## Changelog
354354

355+
### Version v0.7.0-rc.5
356+
357+
- Add deviceListStrategyFlag to allow device list passing as volume mounts
358+
355359
### Version v0.7.0-rc.4
356360

357361
- Allow one to override selector.matchLabels in the helm chart

RELEASE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Publishing the container is automated through gitlab-ci and only requires one to
88
Publishing the helm chart is currently manual, and we should move to an automated process ASAP
99

1010
# Release Process Checklist
11-
- [ ] Update the README to change occurances of the old version (e.g: `v0.7.0-rc.4`) with the new version
11+
- [ ] Update the README to change occurances of the old version (e.g: `v0.7.0-rc.5`) with the new version
1212
- [ ] Update the README changelog
1313
- [ ] Commit, Tag and Push to Gitlab
1414
- [ ] Build a new helm package with `helm package ./deployments/helm/nvidia-device-plugin`

0 commit comments

Comments
 (0)