From c73d9398be5467c1fd02853c06db81f5fc117ac5 Mon Sep 17 00:00:00 2001 From: Kevin Klues Date: Tue, 16 Feb 2021 10:23:51 +0000 Subject: [PATCH] Bump version to v0.8.2 Signed-off-by: Kevin Klues --- Makefile | 2 +- README.md | 34 +++++++++++-------- RELEASE.md | 2 +- .../helm/nvidia-device-plugin/Chart.yaml | 4 +-- ...xtensions-v1beta1-nvidia-device-plugin.yml | 2 +- ...a-device-plugin-compat-with-cpumanager.yml | 2 +- nvidia-device-plugin.yml | 2 +- 7 files changed, 26 insertions(+), 22 deletions(-) diff --git a/Makefile b/Makefile index 33c21546b..8497346d4 100644 --- a/Makefile +++ b/Makefile @@ -23,7 +23,7 @@ ifeq ($(IMAGE),) REGISTRY ?= nvidia IMAGE := $(REGISTRY)/k8s-device-plugin endif -VERSION ?= v0.8.1 +VERSION ?= v0.8.2 ##### Public rules ##### diff --git a/README.md b/README.md index bdb8dfc23..cd9296284 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,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.8.1/nvidia-device-plugin.yml +$ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.8.2/nvidia-device-plugin.yml ``` **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`. Instructions for installing `helm` can be found [here](https://helm.sh/docs/intro/install/). -The `helm` chart for the latest release of the plugin (`v0.8.1`) includes +The `helm` chart for the latest release of the plugin (`v0.8.2`) includes a number of customizable values. The most commonly overridden ones are: ``` @@ -193,7 +193,7 @@ rationale behind this strategy can be found Please take a look in the following `values.yaml` file to see the full set of overridable parameters for the device plugin. -* https://github.com/NVIDIA/k8s-device-plugin/blob/v0.8.1/deployments/helm/nvidia-device-plugin/values.yaml +* https://github.com/NVIDIA/k8s-device-plugin/blob/v0.8.2/deployments/helm/nvidia-device-plugin/values.yaml #### Installing via `helm install`from the `nvidia-device-plugin` `helm` repository @@ -216,7 +216,7 @@ plugin with the various flags from above. Using the default values for the flags: ```shell $ helm install \ - --version=0.8.1 \ + --version=0.8.2 \ --generate-name \ nvdp/nvidia-device-plugin ``` @@ -225,7 +225,7 @@ Enabling compatibility with the `CPUManager` and running with a request for 100ms of CPU time and a limit of 512MB of memory. ```shell $ helm install \ - --version=0.8.1 \ + --version=0.8.2 \ --generate-name \ --set compatWithCPUManager=true \ --set resources.requests.cpu=100m \ @@ -236,7 +236,7 @@ $ helm install \ Use the legacy Daemonset API (only available on Kubernetes < `v1.16`): ```shell $ helm install \ - --version=0.8.1 \ + --version=0.8.2 \ --generate-name \ --set legacyDaemonsetAPI=true \ nvdp/nvidia-device-plugin @@ -245,7 +245,7 @@ $ helm install \ Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy` ```shell $ helm install \ - --version=0.8.1 \ + --version=0.8.2 \ --generate-name \ --set compatWithCPUManager=true \ --set migStrategy=mixed \ @@ -263,7 +263,7 @@ Using the default values for the flags: ```shell $ helm install \ --generate-name \ - https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.1.tgz + https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.2.tgz ``` Enabling compatibility with the `CPUManager` and running with a request for @@ -274,7 +274,7 @@ $ helm install \ --set compatWithCPUManager=true \ --set resources.requests.cpu=100m \ --set resources.limits.memory=512Mi \ - https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.1.tgz + https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.2.tgz ``` Use the legacy Daemonset API (only available on Kubernetes < `v1.16`): @@ -282,7 +282,7 @@ Use the legacy Daemonset API (only available on Kubernetes < `v1.16`): $ helm install \ --generate-name \ --set legacyDaemonsetAPI=true \ - https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.1.tgz + https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.2.tgz ``` Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy` @@ -291,14 +291,14 @@ $ helm install \ --generate-name \ --set compatWithCPUManager=true \ --set migStrategy=mixed \ - https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.1.tgz + https://nvidia.github.com/k8s-device-plugin/stable/nvidia-device-plugin-0.8.2.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.8.1`), but can +It assumes you are pinning to the latest release tag (i.e. `v0.8.2`), but can easily be modified to work with any available tag or branch. ### With Docker @@ -306,8 +306,8 @@ easily be modified to work with any available tag or branch. #### Build 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.8.1 -$ docker tag nvcr.io/nvidia/k8s-device-plugin:v0.8.1 nvcr.io/nvidia/k8s-device-plugin:devel +$ docker pull nvcr.io/nvidia/k8s-device-plugin:v0.8.2 +$ docker tag nvcr.io/nvidia/k8s-device-plugin:v0.8.2 nvcr.io/nvidia/k8s-device-plugin:devel ``` Option 2, build without cloning the repository: @@ -315,7 +315,7 @@ Option 2, build without cloning the repository: $ docker build \ -t nvcr.io/nvidia/k8s-device-plugin:devel \ -f docker/amd64/Dockerfile.ubuntu16.04 \ - https://github.com/NVIDIA/k8s-device-plugin.git#v0.8.1 + https://github.com/NVIDIA/k8s-device-plugin.git#v0.8.2 ``` Option 3, if you want to modify the code: @@ -369,6 +369,10 @@ $ ./k8s-device-plugin --pass-device-specs ## Changelog +### Version v0.8.2 + +- Update all dockerhub references to nvcr.io + ### Version v0.8.1 - Fix permission error when using NewDevice instead of NewDeviceLite when constructing MIG device map diff --git a/RELEASE.md b/RELEASE.md index c084c406f..65f30e6ff 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -9,7 +9,7 @@ Publishing the helm chart is currently manual, and we should move to an automate # Release Process Checklist - [ ] Update the README changelog -- [ ] Update the README to change occurances of the old version (e.g: `v0.8.1`) with the new version +- [ ] Update the README to change occurances of the old version (e.g: `v0.8.2`) with the new version - [ ] Commit, Tag and Push to Gitlab - [ ] Build a new helm package with `helm package ./deployments/helm/nvidia-device-plugin` - [ ] Switch to the `gh-pages` branch and move the newly generated package to the `stable` helm repo diff --git a/deployments/helm/nvidia-device-plugin/Chart.yaml b/deployments/helm/nvidia-device-plugin/Chart.yaml index 9fa2458b3..a9d6c4996 100644 --- a/deployments/helm/nvidia-device-plugin/Chart.yaml +++ b/deployments/helm/nvidia-device-plugin/Chart.yaml @@ -2,7 +2,7 @@ apiVersion: v2 name: nvidia-device-plugin type: application description: A Helm chart for the nvidia-device-plugin on Kubernetes -version: "0.8.1" -appVersion: "0.8.1" +version: "0.8.2" +appVersion: "0.8.2" kubeVersion: ">= 1.10.0-0" home: https://github.com/NVIDIA/k8s-device-plugin diff --git a/deployments/static/extensions-v1beta1-nvidia-device-plugin.yml b/deployments/static/extensions-v1beta1-nvidia-device-plugin.yml index d42b24975..7907e16f2 100644 --- a/deployments/static/extensions-v1beta1-nvidia-device-plugin.yml +++ b/deployments/static/extensions-v1beta1-nvidia-device-plugin.yml @@ -43,7 +43,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.8.1 + - image: nvcr.io/nvidia/k8s-device-plugin:v0.8.2 name: nvidia-device-plugin-ctr args: ["--fail-on-init-error=false"] securityContext: diff --git a/deployments/static/nvidia-device-plugin-compat-with-cpumanager.yml b/deployments/static/nvidia-device-plugin-compat-with-cpumanager.yml index 8f8bb2807..6760e2553 100644 --- a/deployments/static/nvidia-device-plugin-compat-with-cpumanager.yml +++ b/deployments/static/nvidia-device-plugin-compat-with-cpumanager.yml @@ -46,7 +46,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.8.1 + - image: nvcr.io/nvidia/k8s-device-plugin:v0.8.2 name: nvidia-device-plugin-ctr args: ["--fail-on-init-error=false", "--pass-device-specs"] securityContext: diff --git a/nvidia-device-plugin.yml b/nvidia-device-plugin.yml index afb66bc01..130d7ed2d 100644 --- a/nvidia-device-plugin.yml +++ b/nvidia-device-plugin.yml @@ -46,7 +46,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.8.1 + - image: nvcr.io/nvidia/k8s-device-plugin:v0.8.2 name: nvidia-device-plugin-ctr args: ["--fail-on-init-error=false"] securityContext: