Skip to content

Commit e8de9ba

Browse files
committed
Merge branch 'upstream-bump-v0.7.3' into 'master'
Bump version to v0.7.3 See merge request nvidia/kubernetes/device-plugin!68
2 parents bff876e + 6ce1904 commit e8de9ba

File tree

7 files changed

+26
-22
lines changed

7 files changed

+26
-22
lines changed

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ifeq ($(IMAGE),)
2323
REGISTRY ?= nvidia
2424
IMAGE := $(REGISTRY)/k8s-device-plugin
2525
endif
26-
VERSION ?= v0.7.2
26+
VERSION ?= v0.7.3
2727

2828
##### Public rules #####
2929

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.2/nvidia-device-plugin.yml
85+
$ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.7.3/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.2`) includes
126+
The `helm` chart for the latest release of the plugin (`v0.7.3`) includes
127127
a number of customizable values. The most commonly overridden ones are:
128128

129129
```
@@ -191,7 +191,7 @@ rationale behind this strategy can be found
191191
Please take a look in the following `values.yaml` file to see the full set of
192192
overridable parameters for the device plugin.
193193

194-
* https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.2/deployments/helm/nvidia-device-plugin/values.yaml
194+
* https://github.com/NVIDIA/k8s-device-plugin/blob/v0.7.3/deployments/helm/nvidia-device-plugin/values.yaml
195195

196196
#### Installing via `helm install`from the `nvidia-device-plugin` `helm` repository
197197

@@ -214,7 +214,7 @@ plugin with the various flags from above.
214214
Using the default values for the flags:
215215
```shell
216216
$ helm install \
217-
--version=0.7.2 \
217+
--version=0.7.3 \
218218
--generate-name \
219219
nvdp/nvidia-device-plugin
220220
```
@@ -223,7 +223,7 @@ Enabling compatibility with the `CPUManager` and running with a request for
223223
100ms of CPU time and a limit of 512MB of memory.
224224
```shell
225225
$ helm install \
226-
--version=0.7.2 \
226+
--version=0.7.3 \
227227
--generate-name \
228228
--set compatWithCPUManager=true \
229229
--set resources.requests.cpu=100m \
@@ -234,7 +234,7 @@ $ helm install \
234234
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
235235
```shell
236236
$ helm install \
237-
--version=0.7.2 \
237+
--version=0.7.3 \
238238
--generate-name \
239239
--set legacyDaemonsetAPI=true \
240240
nvdp/nvidia-device-plugin
@@ -243,7 +243,7 @@ $ helm install \
243243
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
244244
```shell
245245
$ helm install \
246-
--version=0.7.2 \
246+
--version=0.7.3 \
247247
--generate-name \
248248
--set compatWithCPUManager=true \
249249
--set migStrategy=mixed \
@@ -261,7 +261,7 @@ Using the default values for the flags:
261261
```shell
262262
$ helm install \
263263
--generate-name \
264-
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.2.tgz
264+
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.3.tgz
265265
```
266266

267267
Enabling compatibility with the `CPUManager` and running with a request for
@@ -272,15 +272,15 @@ $ helm install \
272272
--set compatWithCPUManager=true \
273273
--set resources.requests.cpu=100m \
274274
--set resources.limits.memory=512Mi \
275-
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.2.tgz
275+
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.3.tgz
276276
```
277277

278278
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
279279
```shell
280280
$ helm install \
281281
--generate-name \
282282
--set legacyDaemonsetAPI=true \
283-
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.2.tgz
283+
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.3.tgz
284284
```
285285

286286
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
@@ -289,31 +289,31 @@ $ helm install \
289289
--generate-name \
290290
--set compatWithCPUManager=true \
291291
--set migStrategy=mixed \
292-
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.2.tgz
292+
https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.7.3.tgz
293293
```
294294

295295
## Building and Running Locally
296296

297297
The next sections are focused on building the device plugin locally and running it.
298298
It is intended purely for development and testing, and not required by most users.
299-
It assumes you are pinning to the latest release tag (i.e. `v0.7.2`), but can
299+
It assumes you are pinning to the latest release tag (i.e. `v0.7.3`), but can
300300
easily be modified to work with any available tag or branch.
301301

302302
### With Docker
303303

304304
#### Build
305305
Option 1, pull the prebuilt image from [Docker Hub](https://hub.docker.com/r/nvidia/k8s-device-plugin):
306306
```shell
307-
$ docker pull nvidia/k8s-device-plugin:v0.7.2
308-
$ docker tag nvidia/k8s-device-plugin:v0.7.2 nvidia/k8s-device-plugin:devel
307+
$ docker pull nvidia/k8s-device-plugin:v0.7.3
308+
$ docker tag nvidia/k8s-device-plugin:v0.7.3 nvidia/k8s-device-plugin:devel
309309
```
310310

311311
Option 2, build without cloning the repository:
312312
```shell
313313
$ docker build \
314314
-t nvidia/k8s-device-plugin:devel \
315315
-f docker/amd64/Dockerfile.ubuntu16.04 \
316-
https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.2
316+
https://github.com/NVIDIA/k8s-device-plugin.git#v0.7.3
317317
```
318318

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

368368
## Changelog
369369

370+
### Version v0.7.3
371+
372+
- Update vendoring to include bug fix for `nvmlEventSetWait_v2`
373+
370374
### Version v0.7.2
371375

372376
- Fix bug in dockfiles for ubi8 and centos using CMD not ENTRYPOINT

RELEASE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Publishing the helm chart is currently manual, and we should move to an automate
99

1010
# Release Process Checklist
1111
- [ ] Update the README changelog
12-
- [ ] Update the README to change occurances of the old version (e.g: `v0.7.2`) with the new version
12+
- [ ] Update the README to change occurances of the old version (e.g: `v0.7.3`) with the new version
1313
- [ ] Commit, Tag and Push to Gitlab
1414
- [ ] Build a new helm package with `helm package ./deployments/helm/nvidia-device-plugin`
1515
- [ ] Switch to the `gh-pages` branch and move the newly generated package to the `stable` helm repo

deployments/helm/nvidia-device-plugin/Chart.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ apiVersion: v2
22
name: nvidia-device-plugin
33
type: application
44
description: A Helm chart for the nvidia-device-plugin on Kubernetes
5-
version: "0.7.2"
6-
appVersion: "0.7.2"
5+
version: "0.7.3"
6+
appVersion: "0.7.3"
77
kubeVersion: ">= 1.10.0-0"
88
home: https://github.com/NVIDIA/k8s-device-plugin

deployments/static/extensions-v1beta1-nvidia-device-plugin.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ spec:
4343
# See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
4444
priorityClassName: "system-node-critical"
4545
containers:
46-
- image: nvidia/k8s-device-plugin:v0.7.2
46+
- image: nvidia/k8s-device-plugin:v0.7.3
4747
name: nvidia-device-plugin-ctr
4848
args: ["--fail-on-init-error=false"]
4949
securityContext:

deployments/static/nvidia-device-plugin-compat-with-cpumanager.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ spec:
4646
# See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
4747
priorityClassName: "system-node-critical"
4848
containers:
49-
- image: nvidia/k8s-device-plugin:v0.7.2
49+
- image: nvidia/k8s-device-plugin:v0.7.3
5050
name: nvidia-device-plugin-ctr
5151
args: ["--fail-on-init-error=false", "--pass-device-specs"]
5252
securityContext:

nvidia-device-plugin.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ spec:
4646
# See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
4747
priorityClassName: "system-node-critical"
4848
containers:
49-
- image: nvidia/k8s-device-plugin:v0.7.2
49+
- image: nvidia/k8s-device-plugin:v0.7.3
5050
name: nvidia-device-plugin-ctr
5151
args: ["--fail-on-init-error=false"]
5252
securityContext:

0 commit comments

Comments
 (0)