Merge pull request #137 from andrewsykim/release-0.1.18

bump version to 0.1.18

README.md

@@ -7,7 +7,7 @@
 ## Releases
 
 Cloud Controller Manager follows [semantic versioning](https://semver.org/).
-The current version is: **`v0.1.7`**. This means that the project is still
+The current version is: **`v0.1.8`**. 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
@@ -70,15 +70,15 @@ $ git push origin
 
 After it's merged to master, [create a new Github
 release](https://github.com/digitalocean/digitalocean-cloud-controller-manager/releases/new) from
-master with the version `v0.1.7` and then publish a new docker build:
+master with the version `v0.1.8` and then publish a new docker build:
 
 ```
 $ git checkout master
 $ make publish
 ```
 
-This will create a binary with version `v0.1.7` and docker image pushed to
-`digitalocean/digitalocean-cloud-controller-manager:v0.1.7`
+This will create a binary with version `v0.1.8` and docker image pushed to
+`digitalocean/digitalocean-cloud-controller-manager:v0.1.8`
 
 ## Contributing
 

VERSION

@@ -1 +1 @@
-v0.1.7
+v0.1.8

docs/getting-started.md

@@ -10,7 +10,7 @@ These are the recommended versions to run the cloud controller manager based on
 * Use CCM versions >= v0.1.2 if you're running Kubernetes version v1.8
 * Use CCM versions >= v0.1.4 if you're running Kubernetes version v1.9 - v1.10
 * Use CCM versions >= v0.1.5 if you're running Kubernetes version >= v1.10
-* Use CCM versions >= v0.1.7 if you're running Kubernetes version >= v1.11
+* Use CCM versions >= v0.1.8 if you're running Kubernetes version >= v1.11
 
 ### --cloud-provider=external
 All `kubelet`s in your cluster **MUST** set the flag `--cloud-provider=external`. `kube-apiserver` and `kube-controller-manager` must **NOT** set the flag `--cloud-provider` which will default them to use no cloud provider natively.
@@ -90,7 +90,7 @@ digitalocean          Opaque                                1         18h
 Currently we only support alpha release of the `digitalocean-cloud-controller-manager` due to its active development. Run the first alpha release like so
 
 ```bash
-kubectl apply -f releases/v0.1.7.yml
+kubectl apply -f releases/v0.1.8.yml
 deployment "digitalocean-cloud-controller-manager" created
 ```
 

releases/v0.1.8.yml

@@ -0,0 +1,141 @@
+# NOTE: this release is compatible with Kubernetes versions v1.9 - v1.12
+
+---
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: digitalocean-cloud-controller-manager
+  namespace: kube-system
+spec:
+  replicas: 1
+  revisionHistoryLimit: 2
+  template:
+    metadata:
+      labels:
+        app: digitalocean-cloud-controller-manager
+      annotations:
+        scheduler.alpha.kubernetes.io/critical-pod: ''
+    spec:
+      dnsPolicy: Default
+      hostNetwork: true
+      serviceAccountName: cloud-controller-manager
+      tolerations:
+        # this taint is set by all kubelets running `--cloud-provider=external`
+        # so we should tolerate it to schedule the digitalocean ccm
+        - key: "node.cloudprovider.kubernetes.io/uninitialized"
+          value: "true"
+          effect: "NoSchedule"
+        - key: "CriticalAddonsOnly"
+          operator: "Exists"
+        # cloud controller manages should be able to run on masters
+        - key: "node-role.kubernetes.io/master"
+          effect: NoSchedule
+      containers:
+      - image: digitalocean/digitalocean-cloud-controller-manager:v0.1.8
+        name: digitalocean-cloud-controller-manager
+        command:
+          - "/bin/digitalocean-cloud-controller-manager"
+          - "--cloud-provider=digitalocean"
+          - "--leader-elect=false"
+        resources:
+          requests:
+            cpu: 100m
+            memory: 50Mi
+        env:
+          - name: DO_ACCESS_TOKEN
+            valueFrom:
+              secretKeyRef:
+                name: digitalocean
+                key: access-token
+
+---
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: cloud-controller-manager
+  namespace: kube-system
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  annotations:
+    rbac.authorization.kubernetes.io/autoupdate: "true"
+  name: system:cloud-controller-manager
+rules:
+- apiGroups:
+  - ""
+  resources:
+  - events
+  verbs:
+  - create
+  - patch
+  - update
+- apiGroups:
+  - ""
+  resources:
+  - nodes
+  verbs:
+  - '*'
+- apiGroups:
+  - ""
+  resources:
+  - nodes/status
+  verbs:
+  - patch
+- apiGroups:
+  - ""
+  resources:
+  - services
+  verbs:
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - ""
+  resources:
+  - services/status
+  verbs:
+  - list
+  - patch
+  - update
+  - watch
+- apiGroups:
+  - ""
+  resources:
+  - serviceaccounts
+  verbs:
+  - create
+- apiGroups:
+  - ""
+  resources:
+  - persistentvolumes
+  verbs:
+  - get
+  - list
+  - update
+  - watch
+- apiGroups:
+  - ""
+  resources:
+  - endpoints
+  verbs:
+  - create
+  - get
+  - list
+  - watch
+  - update
+---
+kind: ClusterRoleBinding
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: system:cloud-controller-manager
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: system:cloud-controller-manager
+subjects:
+- kind: ServiceAccount
+  name: cloud-controller-manager
+  namespace: kube-system
+