Skip to content

Commit

Permalink
Update RELEASE and README for v0.12.0-rc.5
Browse files Browse the repository at this point in the history
Signed-off-by: Kevin Klues <[email protected]>
  • Loading branch information
klueska committed Jun 1, 2022
1 parent e529960 commit 8de501d
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 16 deletions.
37 changes: 22 additions & 15 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.12.0-rc.4/nvidia-device-plugin.yml
$ kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/v0.12.0-rc.5/nvidia-device-plugin.yml
```

**Note:** This is a simple static daemonset meant to demonstrate the basic
Expand Down Expand Up @@ -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.12.0-rc.4`) includes
The `helm` chart for the latest release of the plugin (`v0.12.0-rc.5`) includes
a number of customizable values. The most commonly overridden ones are:

```
Expand Down Expand Up @@ -207,7 +207,7 @@ attached to them.
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.12.0-rc.4/deployments/helm/nvidia-device-plugin/values.yaml
* https://github.com/NVIDIA/k8s-device-plugin/blob/v0.12.0-rc.5/deployments/helm/nvidia-device-plugin/values.yaml

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

Expand All @@ -230,7 +230,7 @@ plugin with the various flags from above.
Using the default values for the flags:
```shell
$ helm install \
--version=0.12.0-rc.4 \
--version=0.12.0-rc.5 \
--generate-name \
nvdp/nvidia-device-plugin
```
Expand All @@ -239,7 +239,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.12.0-rc.4 \
--version=0.12.0-rc.5 \
--generate-name \
--set compatWithCPUManager=true \
--set resources.requests.cpu=100m \
Expand All @@ -250,7 +250,7 @@ $ helm install \
Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
```shell
$ helm install \
--version=0.12.0-rc.4 \
--version=0.12.0-rc.5 \
--generate-name \
--set legacyDaemonsetAPI=true \
nvdp/nvidia-device-plugin
Expand All @@ -259,7 +259,7 @@ $ helm install \
Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
```shell
$ helm install \
--version=0.12.0-rc.4 \
--version=0.12.0-rc.5 \
--generate-name \
--set compatWithCPUManager=true \
--set migStrategy=mixed \
Expand All @@ -277,7 +277,7 @@ Using the default values for the flags:
```shell
$ helm install \
--generate-name \
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.4.tgz
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.5.tgz
```

Enabling compatibility with the `CPUManager` and running with a request for
Expand All @@ -288,15 +288,15 @@ $ helm install \
--set compatWithCPUManager=true \
--set resources.requests.cpu=100m \
--set resources.limits.memory=512Mi \
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.4.tgz
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.5.tgz
```

Use the legacy Daemonset API (only available on Kubernetes < `v1.16`):
```shell
$ helm install \
--generate-name \
--set legacyDaemonsetAPI=true \
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.4.tgz
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.5.tgz
```

Enabling compatibility with the `CPUManager` and the `mixed` `migStrategy`
Expand All @@ -305,31 +305,31 @@ $ helm install \
--generate-name \
--set compatWithCPUManager=true \
--set migStrategy=mixed \
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.4.tgz
https://nvidia.github.io/k8s-device-plugin/stable/nvidia-device-plugin-0.12.0-rc.5.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.12.0-rc.4`), but can
It assumes you are pinning to the latest release tag (i.e. `v0.12.0-rc.5`), but can
easily be modified to work with any available tag or branch.

### With Docker

#### 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.12.0-rc.4
$ docker tag nvcr.io/nvidia/k8s-device-plugin:v0.12.0-rc.4 nvcr.io/nvidia/k8s-device-plugin:devel
$ docker pull nvcr.io/nvidia/k8s-device-plugin:v0.12.0-rc.5
$ docker tag nvcr.io/nvidia/k8s-device-plugin:v0.12.0-rc.5 nvcr.io/nvidia/k8s-device-plugin:devel
```

Option 2, build without cloning the repository:
```shell
$ docker build \
-t nvcr.io/nvidia/k8s-device-plugin:devel \
-f deployments/container/Dockerfile.ubuntu \
https://github.com/NVIDIA/k8s-device-plugin.git#v0.12.0-rc.4
https://github.com/NVIDIA/k8s-device-plugin.git#v0.12.0-rc.5
```

Option 3, if you want to modify the code:
Expand Down Expand Up @@ -383,6 +383,13 @@ $ ./k8s-device-plugin --pass-device-specs

## Changelog

### Version v0.12.0-rc.5

- Allow either an external ConfigMap name or a set of configs in helm
- Handle cases where no default config is specified to config-manager
- Update API used to pass config files to helm to use map instead of list
- Fix bug that wasn't properly stopping plugins across a soft restart

### Version v0.12.0-rc.4

- Make GFD and NFD (optional) subcharts of the device plugin's helm chart
Expand Down
2 changes: 1 addition & 1 deletion RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.12.0-rc.4`) with the new version
- [ ] Update the README to change occurances of the old version (e.g: `v0.12.0-rc.5`) 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
Expand Down

0 comments on commit 8de501d

Please sign in to comment.