Skip to content

Commit 7613599

Browse files
committed
docs: Add to concepts page
1 parent d6a4cf8 commit 7613599

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

docs/modules/secret-operator/examples/truststore-tls.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,4 @@ metadata:
66
spec:
77
secretClassName: tls # <2>
88
format: tls-pem # <3>
9+
targetKind: ConfigMap # <4>

docs/modules/secret-operator/pages/truststore.adoc

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,12 @@ A TrustStore looks like this:
1212
include::example$truststore-tls.yaml[]
1313
----
1414
<1> Also used to name the created ConfigMap
15-
<2> The name of the xref:secretclass.adoc[]
16-
<3> The requested xref:secretclass.adoc#format[format]
15+
<2> Mandatory name of the xref:secretclass.adoc[]
16+
<3> Optional requested xref:secretclass.adoc#format[format]
17+
<4> Option Kubernetes resource, which should be used to output the requested information to.
18+
Either `ConfigMap` or `Secret`, defaults to `ConfigMap`.
1719

18-
This will create a ConfigMap named `truststore-pem` containing a `ca.crt` with the trust root certificates.
20+
This will create a ConfigMap (or `Secret` based on `targetKind`) named `truststore-pem` containing a `ca.crt` with the trust root certificates.
1921
It can then either be mounted into a Pod or retrieved and used from outside of Kubernetes.
2022

2123
NOTE: Make sure to have a procedure for updating the retrieved certificates.

0 commit comments

Comments
 (0)