deploy: v1.1.0 driver image + Kubernetes 1.14 deployment

This uses the v1.1.0 driver image, which does not exist yet because we
first have update the deployment files before we can tag that release.

The name of the deployment gets changed because it is no longer for
Kubernetes master (although it works there).

Author: pohly

deploy/kubernetes-1.13/hostpath/csi-hostpath-plugin.yaml

@@ -63,7 +63,7 @@ spec:
             name: csi-data-dir
 
         - name: hostpath
-          image: quay.io/k8scsi/hostpathplugin:canary
+          image: quay.io/k8scsi/hostpathplugin:v1.1.0
           args:
             - "--v=5"
             - "--endpoint=$(CSI_ENDPOINT)"

deploy/kubernetes-1.14

@@ -1,11 +1,8 @@
-The deployment for master uses CSI 1.0 and thus is incompatible with
-Kubernetes < 1.13.
+The deployment for Kubernetes 1.14 uses CSI 1.0 and thus is
+incompatible with Kubernetes < 1.13.
 
 It uses the APIs for CSIDriverInfo and CSINodeInfo that were
 introduced in Kubernetes 1.14, so features depending on those (like
 topology) will not work on Kubernetes 1.13. But because this example
 deployment does not enable those features, it can run on Kubernetes
 1.13.
-
-WARNING: this example uses the "canary" images. It can break at any
-time.

deploy/master/README.md deploy/kubernetes-1.14/README.mddeploy/master/README.md renamed to deploy/kubernetes-1.14/README.md

@@ -63,7 +63,7 @@ spec:
             name: csi-data-dir
 
         - name: hostpath
-          image: quay.io/k8scsi/hostpathplugin:canary # TODO: replace with v1.1.0 when it is cut
+          image: quay.io/k8scsi/hostpathplugin:v1.1.0
           args:
             - "--v=5"
             - "--endpoint=$(CSI_ENDPOINT)"