Merge pull request #1197 from elezar/bump-release-v0.17.1

Bump versions to v0.17.1 post-release

Author: elezar

CHANGELOG.md

@@ -1,5 +1,13 @@
 ## Changelog
 
+### Version v0.17.1
+- Ensure that generated CDI specs do not contain `enable-cuda-compat` hooks
+- Remove nvidia.com/gpu.imex-domain label
+- Ignore XID error 109
+- Add `ada-lovelace` architecture label for compute capability 8.9
+- Ensure FAIL_ON_INIT_ERROR boolean env is quoted
+- Honor fail-on-init-error when no resources are found
+
 ### v0.17.0
 - Promote v0.17.0-rc.1 to GA
 

README.md

@@ -147,7 +147,7 @@ Once you have configured the options above on all the GPU nodes in your
 cluster, you can enable GPU support by deploying the following Daemonset:
 
 ```shell
-kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.17.0/deployments/static/nvidia-device-plugin.yml
+kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.17.1/deployments/static/nvidia-device-plugin.yml
 ```
 
 **Note:** This is a simple static daemonset meant to demonstrate the basic
@@ -636,12 +636,12 @@ helm repo add nvdp https://nvidia.github.io/k8s-device-plugin
 helm repo update
 ```
 
-Then verify that the latest release (`v0.17.0`) of the plugin is available:
+Then verify that the latest release (`v0.17.1`) of the plugin is available:
 
 ```shell
 $ helm search repo nvdp --devel
 NAME                     	  CHART VERSION  APP VERSION	DESCRIPTION
-nvdp/nvidia-device-plugin	  0.17.0	 0.17.0		A Helm chart for ...
+nvdp/nvidia-device-plugin	  0.17.1	 0.17.1		A Helm chart for ...
 ```
 
 Once this repo is updated, you can begin installing packages from it to deploy
@@ -653,7 +653,7 @@ The most basic installation command without any options is then:
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
   --namespace nvidia-device-plugin \
   --create-namespace \
-  --version 0.17.0
+  --version 0.17.1
 ```
 
 **Note:** You only need the to pass the `--devel` flag to `helm search repo`
@@ -662,7 +662,7 @@ version (e.g. `<version>-rc.1`). Full releases will be listed without this.
 
 ### Configuring the device plugin's `helm` chart
 
-The `helm` chart for the latest release of the plugin (`v0.17.0`) includes
+The `helm` chart for the latest release of the plugin (`v0.17.1`) includes
 a number of customizable values.
 
 Prior to `v0.12.0` the most commonly used values were those that had direct
@@ -672,7 +672,7 @@ case of the original values is then to override an option from the `ConfigMap`
 if desired. Both methods are discussed in more detail below.
 
 The full set of values that can be set are found here:
-[here](https://github.com/NVIDIA/k8s-device-plugin/blob/v0.17.0/deployments/helm/nvidia-device-plugin/values.yaml).
+[here](https://github.com/NVIDIA/k8s-device-plugin/blob/v0.17.1/deployments/helm/nvidia-device-plugin/values.yaml).
 
 #### Passing configuration to the plugin via a `ConfigMap`
 
@@ -715,7 +715,7 @@ And deploy the device plugin via helm (pointing it at this config file and givin
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set-file config.map.config=/tmp/dp-example-config0.yaml
@@ -740,7 +740,7 @@ kubectl create cm -n nvidia-device-plugin nvidia-plugin-configs \
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set config.name=nvidia-plugin-configs
@@ -770,7 +770,7 @@ And redeploy the device plugin via helm (pointing it at both configs with a spec
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set config.default=config0 \
@@ -792,7 +792,7 @@ kubectl create cm -n nvidia-device-plugin nvidia-plugin-configs \
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set config.default=config0 \
@@ -878,7 +878,7 @@ runtimeClassName:
 ```
 
 Please take a look in the
-[`values.yaml`](https://github.com/NVIDIA/k8s-device-plugin/blob/v0.17.0/deployments/helm/nvidia-device-plugin/values.yaml)
+[`values.yaml`](https://github.com/NVIDIA/k8s-device-plugin/blob/v0.17.1/deployments/helm/nvidia-device-plugin/values.yaml)
 file to see the full set of overridable parameters for the device plugin.
 
 Examples of setting these options include:
@@ -888,7 +888,7 @@ Enabling compatibility with the `CPUManager` and running with a request for
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set compatWithCPUManager=true \
@@ -900,7 +900,7 @@ Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`.
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set compatWithCPUManager=true \
@@ -919,7 +919,7 @@ To enable it, simply set `gfd.enabled=true` during helm install.
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version=0.17.0 \
+  --version=0.17.1 \
   --namespace nvidia-device-plugin \
   --create-namespace \
   --set gfd.enabled=true
@@ -977,13 +977,13 @@ helm repo add nvdp https://nvidia.github.io/k8s-device-plugin
 helm repo update
 ```
 
-Then verify that the latest release (`v0.17.0`) of the plugin is available
+Then verify that the latest release (`v0.17.1`) of the plugin is available
 (Note that this includes the GFD chart):
 
 ```shell
 helm search repo nvdp --devel
 NAME                     	  CHART VERSION  APP VERSION	DESCRIPTION
-nvdp/nvidia-device-plugin	  0.17.0	 0.17.0		A Helm chart for ...
+nvdp/nvidia-device-plugin	  0.17.1	 0.17.1		A Helm chart for ...
 ```
 
 Once this repo is updated, you can begin installing packages from it to deploy
@@ -993,7 +993,7 @@ The most basic installation command without any options is then:
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-  --version 0.17.0 \
+  --version 0.17.1 \
   --namespace gpu-feature-discovery \
   --create-namespace \
   --set devicePlugin.enabled=false
@@ -1004,7 +1004,7 @@ the default namespace.
 
 ```shell
 helm upgrade -i nvdp nvdp/nvidia-device-plugin \
-    --version=0.17.0 \
+    --version=0.17.1 \
     --set allowDefaultNamespace=true \
     --set nfd.enabled=false \
     --set migStrategy=mixed \
@@ -1028,14 +1028,14 @@ Using the default values for the flags:
 helm upgrade -i nvdp \
   --namespace nvidia-device-plugin \
   --create-namespace \
-  https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.17.0.tgz
+  https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.17.1.tgz
 ```
 
 ## Building and Running Locally
 
 The next sections are focused on building the device plugin locally and running it.
 It is intended purely for development and testing, and not required by most users.
-It assumes you are pinning to the latest release tag (i.e. `v0.17.0`), but can
+It assumes you are pinning to the latest release tag (i.e. `v0.17.1`), but can
 easily be modified to work with any available tag or branch.
 
 ### With Docker
@@ -1045,8 +1045,8 @@ easily be modified to work with any available tag or branch.
 Option 1, pull the prebuilt image from [Docker Hub](https://hub.docker.com/r/nvidia/k8s-device-plugin):
 
 ```shell
-docker pull nvcr.io/nvidia/k8s-device-plugin:v0.17.0
-docker tag nvcr.io/nvidia/k8s-device-plugin:v0.17.0 nvcr.io/nvidia/k8s-device-plugin:devel
+docker pull nvcr.io/nvidia/k8s-device-plugin:v0.17.1
+docker tag nvcr.io/nvidia/k8s-device-plugin:v0.17.1 nvcr.io/nvidia/k8s-device-plugin:devel
 ```
 
 Option 2, build without cloning the repository:
@@ -1055,7 +1055,7 @@ Option 2, build without cloning the repository:
 docker build \
   -t nvcr.io/nvidia/k8s-device-plugin:devel \
   -f deployments/container/Dockerfile.ubuntu \
-  https://github.com/NVIDIA/k8s-device-plugin.git#v0.17.0
+  https://github.com/NVIDIA/k8s-device-plugin.git#v0.17.1
 ```
 
 Option 3, if you want to modify the code:

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

@@ -2,8 +2,8 @@ apiVersion: v2
 name: nvidia-device-plugin
 type: application
 description: A Helm chart for the nvidia-device-plugin on Kubernetes
-version: "0.17.0"
-appVersion: "0.17.0"
+version: "0.17.1"
+appVersion: "0.17.1"
 kubeVersion: ">= 1.10.0-0"
 home: https://github.com/NVIDIA/k8s-device-plugin
 

deployments/static/gpu-feature-discovery-daemonset-with-mig-mixed.yaml

@@ -4,7 +4,7 @@ metadata:
   name: gpu-feature-discovery
   labels:
     app.kubernetes.io/name: gpu-feature-discovery
-    app.kubernetes.io/version: 0.17.0
+    app.kubernetes.io/version: 0.17.1
     app.kubernetes.io/part-of: nvidia-gpu
 spec:
   selector:
@@ -15,11 +15,11 @@ spec:
     metadata:
       labels:
         app.kubernetes.io/name: gpu-feature-discovery
-        app.kubernetes.io/version: 0.17.0
+        app.kubernetes.io/version: 0.17.1
         app.kubernetes.io/part-of: nvidia-gpu
     spec:
       containers:
-        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
           name: gpu-feature-discovery
           command: ["/usr/bin/gpu-feature-discovery"]
           volumeMounts:

deployments/static/gpu-feature-discovery-daemonset-with-mig-single.yaml

@@ -4,7 +4,7 @@ metadata:
   name: gpu-feature-discovery
   labels:
     app.kubernetes.io/name: gpu-feature-discovery
-    app.kubernetes.io/version: 0.17.0
+    app.kubernetes.io/version: 0.17.1
     app.kubernetes.io/part-of: nvidia-gpu
 spec:
   selector:
@@ -15,11 +15,11 @@ spec:
     metadata:
       labels:
         app.kubernetes.io/name: gpu-feature-discovery
-        app.kubernetes.io/version: 0.17.0
+        app.kubernetes.io/version: 0.17.1
         app.kubernetes.io/part-of: nvidia-gpu
     spec:
       containers:
-        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
           name: gpu-feature-discovery
           command: ["/usr/bin/gpu-feature-discovery"]
           volumeMounts:

deployments/static/gpu-feature-discovery-daemonset.yaml

@@ -4,7 +4,7 @@ metadata:
   name: gpu-feature-discovery
   labels:
     app.kubernetes.io/name: gpu-feature-discovery
-    app.kubernetes.io/version: 0.17.0
+    app.kubernetes.io/version: 0.17.1
     app.kubernetes.io/part-of: nvidia-gpu
 spec:
   selector:
@@ -15,11 +15,11 @@ spec:
     metadata:
       labels:
         app.kubernetes.io/name: gpu-feature-discovery
-        app.kubernetes.io/version: 0.17.0
+        app.kubernetes.io/version: 0.17.1
         app.kubernetes.io/part-of: nvidia-gpu
     spec:
       containers:
-        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
           name: gpu-feature-discovery
           command: ["/usr/bin/gpu-feature-discovery"]
           volumeMounts:

deployments/static/gpu-feature-discovery-job.yaml.template

@@ -4,19 +4,19 @@ metadata:
   name: gpu-feature-discovery
   labels:
     app.kubernetes.io/name: gpu-feature-discovery
-    app.kubernetes.io/version: 0.17.0
+    app.kubernetes.io/version: 0.17.1
     app.kubernetes.io/part-of: nvidia-gpu
 spec:
   template:
     metadata:
       labels:
         app.kubernetes.io/name: gpu-feature-discovery
-        app.kubernetes.io/version: 0.17.0
+        app.kubernetes.io/version: 0.17.1
         app.kubernetes.io/part-of: nvidia-gpu
     spec:
       nodeName: NODE_NAME
       containers:
-        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+        - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
           name: gpu-feature-discovery
           command: ["/usr/bin/gpu-feature-discovery"]
           args:

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

@@ -38,7 +38,7 @@ spec:
       # See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
       priorityClassName: "system-node-critical"
       containers:
-      - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+      - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
         name: nvidia-device-plugin-ctr
         env:
           - name: FAIL_ON_INIT_ERROR

deployments/static/nvidia-device-plugin.yml

@@ -38,7 +38,7 @@ spec:
       # See https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
       priorityClassName: "system-node-critical"
       containers:
-      - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.0
+      - image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
         name: nvidia-device-plugin-ctr
         env:
           - name: FAIL_ON_INIT_ERROR

versions.mk

@@ -17,7 +17,7 @@ MODULE := github.com/NVIDIA/$(DRIVER_NAME)
 
 REGISTRY ?= nvcr.io/nvidia
 
-VERSION ?= v0.17.0
+VERSION ?= v0.17.1
 
 # vVERSION represents the version with a guaranteed v-prefix
 vVERSION := v$(VERSION:v%=%)