From a63c5c4fc172fdba1792a49b1f38897b9b4b2aad Mon Sep 17 00:00:00 2001 From: Timo Reimann Date: Tue, 19 Mar 2019 10:04:52 +0100 Subject: [PATCH] Prepare release v0.1.11 - Bump version. - Update change log. - Update manifests. --- CHANGELOG.md | 2 +- README.md | 8 +- VERSION | 2 +- .../cloud-controller-manager.yml | 2 +- docs/getting-started.md | 2 +- releases/v0.1.11.yml | 139 ++++++++++++++++++ 6 files changed, 147 insertions(+), 8 deletions(-) create mode 100644 releases/v0.1.11.yml diff --git a/CHANGELOG.md b/CHANGELOG.md index 4d1139a6a..555740c69 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # CHANGELOG -## unreleased +## v0.1.11 (beta) - Mar 19th 2019 * loadbalancers: add support for PROXY protocol (@timoreimann) * loadbalancers: support numeric health check parameters (@timoreimann) diff --git a/README.md b/README.md index 1220fab8e..0c1eca81d 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ ## Releases Cloud Controller Manager follows [semantic versioning](https://semver.org/). -The current version is: **`v0.1.10`**. This means that the project is still +The current version is: **`v0.1.11`**. 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.10` and then publish a new docker build: +master with the version `v0.1.11` and then publish a new docker build: ```bash git checkout master make publish ``` -This will create a binary with version `v0.1.10` and docker image pushed to -`digitalocean/digitalocean-cloud-controller-manager:v0.1.10` +This will create a binary with version `v0.1.11` and docker image pushed to +`digitalocean/digitalocean-cloud-controller-manager:v0.1.11` ## Contributing diff --git a/VERSION b/VERSION index bf42c7d4e..003492118 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -v0.1.10 +v0.1.11 diff --git a/docs/example-manifests/cloud-controller-manager.yml b/docs/example-manifests/cloud-controller-manager.yml index c5a771787..4b30bf8a9 100644 --- a/docs/example-manifests/cloud-controller-manager.yml +++ b/docs/example-manifests/cloud-controller-manager.yml @@ -47,7 +47,7 @@ spec: operator: Exists tolerationSeconds: 300 containers: - - image: digitalocean/digitalocean-cloud-controller-manager:v0.1.10 + - image: digitalocean/digitalocean-cloud-controller-manager:v0.1.11 name: digitalocean-cloud-controller-manager command: - "/bin/digitalocean-cloud-controller-manager" diff --git a/docs/getting-started.md b/docs/getting-started.md index 849a0a0ce..dc1d29f9b 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -112,7 +112,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.10.yml +kubectl apply -f releases/v0.1.11.yml deployment "digitalocean-cloud-controller-manager" created ``` diff --git a/releases/v0.1.11.yml b/releases/v0.1.11.yml new file mode 100644 index 000000000..f987f21b1 --- /dev/null +++ b/releases/v0.1.11.yml @@ -0,0 +1,139 @@ +--- +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.11 + 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 +