Skip to content

Commit ab3ffea

Browse files
waynrwaynr
authored
Prepare release v0.1.26 (#330)
1 parent 1f7ab14 commit ab3ffea

File tree

6 files changed

+164
-4
lines changed

6 files changed

+164
-4
lines changed

‎CHANGELOG.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# CHANGELOG
22

3+
## v0.1.26 (beta) - June 16th 2020
4+
5+
* Update Kubernetes dependences to 1.18.3 (@waynr)
6+
37
## v0.1.25 (beta) - June 15th 2020
48

59
* Support disowning LBs (@timoreimann)

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
## Releases
88

99
Cloud Controller Manager follows [semantic versioning](https://semver.org/).
10-
The current version is: **`v0.1.25`**. This means that the project is still
10+
The current version is: **`v0.1.26`**. This means that the project is still
1111
under active development and may not be production ready. The plugin will be
1212
bumped to **`v1.0.0`** once the [DigitalOcean Kubernetes
1313
product](https://www.digitalocean.com/products/kubernetes/) is released and

‎VERSION‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v0.1.25
1+
v0.1.26

‎docs/example-manifests/cloud-controller-manager.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ spec:
4747
operator: Exists
4848
tolerationSeconds: 300
4949
containers:
50-
- image: digitalocean/digitalocean-cloud-controller-manager:v0.1.25
50+
- image: digitalocean/digitalocean-cloud-controller-manager:v0.1.26
5151
name: digitalocean-cloud-controller-manager
5252
command:
5353
- "/bin/digitalocean-cloud-controller-manager"

‎docs/getting-started.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ digitalocean Opaque 1 18h
150150
Currently we only support alpha release of the `digitalocean-cloud-controller-manager` due to its active development. Run the first alpha release like so
151151

152152
```bash
153-
kubectl apply -f releases/v0.1.25.yml
153+
kubectl apply -f releases/v0.1.26.yml
154154
deployment "digitalocean-cloud-controller-manager" created
155155
```
156156

‎releases/v0.1.26.yml‎

Lines changed: 156 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,156 @@
1+
---
2+
apiVersion: apps/v1
3+
kind: Deployment
4+
metadata:
5+
name: digitalocean-cloud-controller-manager
6+
namespace: kube-system
7+
spec:
8+
replicas: 1
9+
revisionHistoryLimit: 2
10+
selector:
11+
matchLabels:
12+
app: digitalocean-cloud-controller-manager
13+
template:
14+
metadata:
15+
labels:
16+
app: digitalocean-cloud-controller-manager
17+
annotations:
18+
scheduler.alpha.kubernetes.io/critical-pod: ''
19+
spec:
20+
dnsPolicy: Default
21+
hostNetwork: true
22+
serviceAccountName: cloud-controller-manager
23+
tolerations:
24+
# this taint is set by all kubelets running `--cloud-provider=external`
25+
# so we should tolerate it to schedule the digitalocean ccm
26+
- key: "node.cloudprovider.kubernetes.io/uninitialized"
27+
value: "true"
28+
effect: "NoSchedule"
29+
- key: "CriticalAddonsOnly"
30+
operator: "Exists"
31+
# cloud controller manages should be able to run on masters
32+
- key: "node-role.kubernetes.io/master"
33+
effect: NoSchedule
34+
containers:
35+
- image: digitalocean/digitalocean-cloud-controller-manager:v0.1.26
36+
name: digitalocean-cloud-controller-manager
37+
command:
38+
- "/bin/digitalocean-cloud-controller-manager"
39+
- "--leader-elect=false"
40+
resources:
41+
requests:
42+
cpu: 100m
43+
memory: 50Mi
44+
env:
45+
- name: DO_ACCESS_TOKEN
46+
valueFrom:
47+
secretKeyRef:
48+
name: digitalocean
49+
key: access-token
50+
51+
---
52+
apiVersion: v1
53+
kind: ServiceAccount
54+
metadata:
55+
name: cloud-controller-manager
56+
namespace: kube-system
57+
---
58+
apiVersion: rbac.authorization.k8s.io/v1
59+
kind: ClusterRole
60+
metadata:
61+
annotations:
62+
rbac.authorization.kubernetes.io/autoupdate: "true"
63+
name: system:cloud-controller-manager
64+
rules:
65+
# The following is necessary to support leader election when running DO-CCM on
66+
# a multi-master cluster. We leave it commented out on the assumption that the
67+
# typical user is not running a multi-master cluster and therefore does not
68+
# need the additional persmissions.
69+
#
70+
# - apiGroups:
71+
# - coordination.k8s.io
72+
# resources:
73+
# - leases
74+
# verbs:
75+
# - get
76+
# - watch
77+
# - list
78+
# - create
79+
# - update
80+
# - delete
81+
- apiGroups:
82+
- ""
83+
resources:
84+
- events
85+
verbs:
86+
- create
87+
- patch
88+
- update
89+
- apiGroups:
90+
- ""
91+
resources:
92+
- nodes
93+
verbs:
94+
- '*'
95+
- apiGroups:
96+
- ""
97+
resources:
98+
- nodes/status
99+
verbs:
100+
- patch
101+
- apiGroups:
102+
- ""
103+
resources:
104+
- services
105+
verbs:
106+
- list
107+
- patch
108+
- update
109+
- watch
110+
- apiGroups:
111+
- ""
112+
resources:
113+
- services/status
114+
verbs:
115+
- list
116+
- patch
117+
- update
118+
- watch
119+
- apiGroups:
120+
- ""
121+
resources:
122+
- serviceaccounts
123+
verbs:
124+
- create
125+
- apiGroups:
126+
- ""
127+
resources:
128+
- persistentvolumes
129+
verbs:
130+
- get
131+
- list
132+
- update
133+
- watch
134+
- apiGroups:
135+
- ""
136+
resources:
137+
- endpoints
138+
verbs:
139+
- create
140+
- get
141+
- list
142+
- watch
143+
- update
144+
---
145+
kind: ClusterRoleBinding
146+
apiVersion: rbac.authorization.k8s.io/v1
147+
metadata:
148+
name: system:cloud-controller-manager
149+
roleRef:
150+
apiGroup: rbac.authorization.k8s.io
151+
kind: ClusterRole
152+
name: system:cloud-controller-manager
153+
subjects:
154+
- kind: ServiceAccount
155+
name: cloud-controller-manager
156+
namespace: kube-system

0 commit comments

Comments
 (0)