Skip to content

Commit 42b7f0b

Browse files
committed
Add certManager example yaml
1 parent e6833db commit 42b7f0b

File tree

1 file changed

+22
-1
lines changed

1 file changed

+22
-1
lines changed

src/current/v25.2/deploy-cockroachdb-with-cockroachdb-operator.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -340,7 +340,28 @@ For bare metal deployments, the specific Kubernetes infrastructure deployment st
340340
The subject alternative names are based on a release called `my-release` in the `cockroach-ns` namespace. Make sure they match the services created with the release during Helm install.
341341
{{site.data.alerts.end}}
342342

343-
If you wish to supply certificates with [cert-manager](https://cert-manager.io/), set `cockroachdb.tls.certManager.enabled` to `true`, and `cockroachdb.tls.certManager.issuer` to an IssuerRef (as they appear in certificate resources) pointing to a clusterIssuer or issuer that you have set up in the cluster. The following Kubernetes application describes an example issuer:
343+
If you wish to supply certificates with [cert-manager](https://cert-manager.io/), set `cockroachdb.tls.certManager.enabled` to `true`, and `cockroachdb.tls.certManager.issuer` to an IssuerRef (as they appear in certificate resources) pointing to a clusterIssuer or issuer that you have set up in the cluster:
344+
345+
~~~ yaml
346+
cockroachdb:
347+
tls:
348+
enabled: true
349+
certManager:
350+
enabled: true
351+
caConfigMap: cockroachdb-ca
352+
nodeSecret: cockroachdb-node
353+
clientRootSecret: cockroachdb-root
354+
issuer:
355+
group: cert-manager.io
356+
kind: Issuer
357+
name: cockroachdb-cert-issuer
358+
clientCertDuration: 672h
359+
clientCertExpiryWindow: 48h
360+
nodeCertDuration: 8760h
361+
nodeCertExpiryWindow: 168h
362+
~~~
363+
364+
The following Kubernetes application describes an example issuer.
344365

345366
~~~ yaml
346367
apiVersion: v1

0 commit comments

Comments
 (0)