You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixes#160
## Changelog
### Added
* [chart+kustomize]
* what: Added get secrets permissions for operator namespace.
* why: Necessary for operator to get secrets with certificates.
* [api]
* what: Added helper functions to let getting settings easier.
* why: Unify getting settings throughout the project code.
* [api]
* what: Added ServerTrustedCASecret to spec.
* why: Necessary to mount this certificate to let operator trust etcd
cluster.
* **[controller]**
* **what: Added functionality to disable and enable auth, add root role,
root user.**
* **why: Necessary for the customer.**
### Changed
* [api]
* what: Adjusted field descriptions for security fields.
* why: Necessary to let customers know where we expect created secrets
with certificates.
* [etcdcluster_controller_test]
* what: Commented autotests that reconcile twice and set sts ready.
* why: Not clear how to handle failed tests. It is not supposed to set
ready status when it is not ready. Creating mocks for every function
that uses etcdClient will take much time in the future
Copy file name to clipboardExpand all lines: charts/etcd-operator/crds/etcd-cluster.yaml
+22-4Lines changed: 22 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -202,25 +202,43 @@ spec:
202
202
security:
203
203
description: Security describes security settings of etcd (authentication, certificates, rbac)
204
204
properties:
205
+
enableAuth:
206
+
description: Section to enable etcd auth
207
+
type: boolean
205
208
tls:
206
209
description: Section for user-managed tls certificates
207
210
properties:
208
211
clientSecret:
209
-
description: Client certificate for etcd-operator to do maintenance. It is expected to have tls.crt and tls.key fields in the secret.
212
+
description: |-
213
+
Client certificate for etcd-operator to do maintenance. It is expected to have tls.crt and tls.key fields in the secret.
214
+
This secret must be created in the namespace with etcdCluster CR.
210
215
type: string
211
216
clientTrustedCASecret:
212
-
description: Trusted CA for client certificates that are provided by client to etcd. It is expected to have tls.crt field in the secret.
217
+
description: |-
218
+
Trusted CA for client certificates that are provided by client to etcd. It is expected to have ca.crt field in the secret.
219
+
This secret must be created in the namespace with etcdCluster CR.
213
220
type: string
214
221
peerSecret:
215
-
description: Certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt and tls.key fields in the secret.
222
+
description: |-
223
+
Certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt and tls.key fields in the secret.
224
+
This secret must be created in the namespace with etcdCluster CR.
216
225
type: string
217
226
peerTrustedCASecret:
218
-
description: Trusted CA certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt field in the secret.
227
+
description: |-
228
+
Trusted CA certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have ca.crt field in the secret.
229
+
This secret must be created in the namespace with etcdCluster CR.
219
230
type: string
220
231
serverSecret:
221
232
description: |-
222
233
Server certificate secret to secure client-server communication. Is provided to the client who connects to etcd by client port (2379 by default).
223
234
It is expected to have tls.crt and tls.key fields in the secret.
235
+
This secret must be created in the namespace with etcdCluster CR.
236
+
type: string
237
+
serverTrustedCASecret:
238
+
description: |-
239
+
Trusted CA for etcd server certificates for client-server communication. Is necessary to set trust between operator and etcd.
240
+
It is expected to have ca.crt field in the secret. If it is not specified, then insecure communication will be used.
241
+
This secret must be created in the namespace with etcdCluster CR.
Copy file name to clipboardExpand all lines: config/crd/bases/etcd.aenix.io_etcdclusters.yaml
+22-4Lines changed: 22 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -192,25 +192,43 @@ spec:
192
192
security:
193
193
description: Security describes security settings of etcd (authentication, certificates, rbac)
194
194
properties:
195
+
enableAuth:
196
+
description: Section to enable etcd auth
197
+
type: boolean
195
198
tls:
196
199
description: Section for user-managed tls certificates
197
200
properties:
198
201
clientSecret:
199
-
description: Client certificate for etcd-operator to do maintenance. It is expected to have tls.crt and tls.key fields in the secret.
202
+
description: |-
203
+
Client certificate for etcd-operator to do maintenance. It is expected to have tls.crt and tls.key fields in the secret.
204
+
This secret must be created in the namespace with etcdCluster CR.
200
205
type: string
201
206
clientTrustedCASecret:
202
-
description: Trusted CA for client certificates that are provided by client to etcd. It is expected to have tls.crt field in the secret.
207
+
description: |-
208
+
Trusted CA for client certificates that are provided by client to etcd. It is expected to have ca.crt field in the secret.
209
+
This secret must be created in the namespace with etcdCluster CR.
203
210
type: string
204
211
peerSecret:
205
-
description: Certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt and tls.key fields in the secret.
212
+
description: |-
213
+
Certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt and tls.key fields in the secret.
214
+
This secret must be created in the namespace with etcdCluster CR.
206
215
type: string
207
216
peerTrustedCASecret:
208
-
description: Trusted CA certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have tls.crt field in the secret.
217
+
description: |-
218
+
Trusted CA certificate secret to secure peer-to-peer communication between etcd nodes. It is expected to have ca.crt field in the secret.
219
+
This secret must be created in the namespace with etcdCluster CR.
209
220
type: string
210
221
serverSecret:
211
222
description: |-
212
223
Server certificate secret to secure client-server communication. Is provided to the client who connects to etcd by client port (2379 by default).
213
224
It is expected to have tls.crt and tls.key fields in the secret.
225
+
This secret must be created in the namespace with etcdCluster CR.
226
+
type: string
227
+
serverTrustedCASecret:
228
+
description: |-
229
+
Trusted CA for etcd server certificates for client-server communication. Is necessary to set trust between operator and etcd.
230
+
It is expected to have ca.crt field in the secret. If it is not specified, then insecure communication will be used.
231
+
This secret must be created in the namespace with etcdCluster CR.
0 commit comments