update deployment manifests and release instructions

Makefile

@@ -24,12 +24,12 @@ export GO111MODULE=on
 
 all: linode
 
+vendor:
+	go mod vendor
 test:
 	go test -v ./... -cover
 	go vet ./...
-vendor: 
-	go mod vendor
-linode: vendor
+linode: vendor test
 	CGO_ENABLED=0 GOOS=linux go build -a -ldflags '-X main.vendorVersion=$(REV) -extldflags "-static"' -o _output/linode ./app/linode
 linode-container: linode
 	docker build -t $(IMAGE_TAG) -f ./app/linode/Dockerfile .

README.md

@@ -62,7 +62,7 @@ linode          Opaque                                2         18h
 The following command will deploy the CSI driver with the related Kubernetes volume attachment, driver registration, and provisioning sidecars:
 
 ```sh
-kubectl apply -f https://raw.githubusercontent.com/linode/linode-blockstorage-csi-driver/master/pkg/linode-bs/deploy/releases/linode-blockstorage-csi-driver-v0.0.3.yaml
+kubectl apply -f https://raw.githubusercontent.com/linode/linode-blockstorage-csi-driver/master/pkg/linode-bs/deploy/releases/linode-blockstorage-csi-driver-v0.1.2.yaml
 ```
 
 This deployment is a concatenation of all of the `yaml` files in [pkg/linode-bs/deploy/kubernetes/](https://github.com/linode/linode-blockstorage-csi-driver/tree/master/pkg/linode-bs/deploy/kubernetes/).
@@ -134,6 +134,17 @@ persistence
 
 Want to improve the linode-blockstorage-csi-driver? Please start [here](.github/CONTRIBUTING.md).
 
+## Doing a Release
+
+1. Open up the Makefile.
+1. Check that the `IMAGE_VERSION` variable is set to the value that you want. You should always start with a `canary` release.
+1. run `make push`. As of this writing, the `push` target depends upon the `linode-container`, `linode`, `vendor, and `test` targets. So the code should be vendored, the tests should run, the build should run, a container should be built, and it should be pushed to the container registry.
+1. Test the new canary version on a live cluster.
+1. Change `IMAGE_VERSION` to the new version of the CSI driver, for exmaple `v0.2.1`
+1. Run `make push` again
+1. Push a git tag for the new version, perferrably pgp signed.
+1. Make a GitHub release and write the release notes for the release.
+
 ## Join us on Slack
 
 For general help or discussion, join the [Kubernetes Slack](http://slack.k8s.io/) channel [#linode](https://kubernetes.slack.com/messages/CD4B15LUR).