Skip to content

Commit

Permalink
Release csi-digitalocean v0.4.1
Browse files Browse the repository at this point in the history
* Cherry-pick: Add tagging support for Volumes via the new `--do-tag` flag
  [[GH-130]](#130)
* Cherry-pick: Fix support for volume snapshots by setting snapshot id on volume creation
  [[GH-129]](#129)
* Cherry-pick: Goreportcard fixes (typos, exported variables, etc..)
  [[GH-121]](#121)
* Cherry-pick: Rename the cluster role bindings for the `node-driver-registrar` to be
  consistent with the other role bindings.
  [[GH-118]](#118)
* Cherry-pick: Remove the `--token` flag for the `csi-do-node` driver. Drivers running on
  the node don't need the token anymore.
  [[GH-118]](#118)
* Cherry-pick: Don't check the volume limits on the worker nodes (worker nodes are not able
  to talk to DigitalOcean API)
  [[GH-142]](#142)
* Cherry-pick: Update `godo` (DigitalOcean API package) version to v1.13.0
  [[GH-143]](#143)
* Cherry-pick: Fix race in snapshot integration test.
  [[GH-146]](#146)
* Cherry-pick: Add tagging support for Volume snapshots via the new `--do-tag` flag
  [[GH-145]](#145)
  • Loading branch information
jcodybaker committed Apr 26, 2019
1 parent e5a9941 commit 16ed9cf
Show file tree
Hide file tree
Showing 4 changed files with 552 additions and 7 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
## unreleased

## v0.4.1 - 2019.04.26

* Cherry-pick: Add tagging support for Volumes via the new `--do-tag` flag
[[GH-130]](https://github.com/digitalocean/csi-digitalocean/pull/130)
* Cherry-pick: Fix support for volume snapshots by setting snapshot id on volume creation
Expand Down
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Cloud Foundry. Feel free to test it on other CO's and give us a feedback.
## Releases

The DigitalOcean CSI plugin follows [semantic versioning](https://semver.org/).
The current version is: **`v0.4.0`**. This means that the project is still
The current version is: **`v0.4.1`**. This means that the project is still
under active development and may not be production ready. The plugin will be
bumped to **`v1.0.0`** once the [DigitalOcean Kubernetes
product](https://www.digitalocean.com/products/kubernetes/) is released and
Expand Down Expand Up @@ -75,10 +75,10 @@ digitalocean Opaque 1 18h

Before you continue, be sure to checkout to a [tagged
release](https://github.com/digitalocean/csi-digitalocean/releases). Always use the [latest stable version](https://github.com/digitalocean/csi-digitalocean/releases/latest)
For example, to use the latest stable version (`v0.4.0`) you can execute the following command:
For example, to use the latest stable version (`v0.4.1`) you can execute the following command:

```
$ kubectl apply -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v0.4.0.yaml
$ kubectl apply -f https://raw.githubusercontent.com/digitalocean/csi-digitalocean/master/deploy/kubernetes/releases/csi-digitalocean-v0.4.1.yaml
```

This file will be always updated to point to the latest stable release. If you
Expand Down Expand Up @@ -207,15 +207,15 @@ $ git push origin

After it's merged to master, [create a new Github
release](https://github.com/digitalocean/csi-digitalocean/releases/new) from
master with the version `v0.4.0` and then publish a new docker build:
master with the version `v0.4.1` and then publish a new docker build:

```
$ git checkout master
$ make publish
```

This will create a binary with version `v0.4.0` and docker image pushed to
`digitalocean/do-csi-plugin:v0.4.0`
This will create a binary with version `v0.4.1` and docker image pushed to
`digitalocean/do-csi-plugin:v0.4.1`

## Contributing

Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v0.4.0
v0.4.1
Loading

0 comments on commit 16ed9cf

Please sign in to comment.