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
Copy file name to clipboardExpand all lines: README.md
+37-1Lines changed: 37 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,42 @@ controller can be used...
12
12
Please check the `examples/example-ca.yaml` how to use the controller after deploying it and using it with cert-manager but
13
13
it also works with normal Kubernetes secrets of type TLS.
14
14
15
+
## Configuration
16
+
17
+
### Required annotations
18
+
19
+
The controller watches secrets of type `kubernetes.io/tls` that carry the following annotations. Set them via cert-manager's `secretTemplate` or directly on a hand-crafted secret.
20
+
21
+
| Annotation | Description |
22
+
|---|---|
23
+
|`sebastian.gaiser.bayern/tls-strimzi-ca: "reconcile"`| Opt the secret into reconciliation |
24
+
|`sebastian.gaiser.bayern/target-cluster-name`| Name of the Strimzi Kafka cluster |
25
+
|`sebastian.gaiser.bayern/target-secret-name`| Name of the target certificate secret (receives `ca.crt` and `tls.crt`) |
26
+
|`sebastian.gaiser.bayern/target-secret-key-name`| Name of the target private key secret (receives `ca.key`) |
27
+
28
+
### Private key rotation policy
29
+
30
+
By default the controller keeps the private key secret in sync with the source secret on every reconciliation. If you configure cert-manager to never rotate the private key (`rotationPolicy: Never`), you should tell the controller the same so it does not overwrite the key secret on certificate renewals.
31
+
32
+
Add the annotation `sebastian.gaiser.bayern/rotation-policy: "Never"` to the cert-manager `secretTemplate`. Use a YAML anchor to reference the value from `privateKey.rotationPolicy` directly so both fields are always in sync:
0 commit comments