File tree Expand file tree Collapse file tree 2 files changed +6
-3
lines changed
docs/modules/secret-operator Expand file tree Collapse file tree 2 files changed +6
-3
lines changed Original file line number Diff line number Diff line change @@ -6,3 +6,4 @@ metadata:
6
6
spec :
7
7
secretClassName : tls # <2>
8
8
format : tls-pem # <3>
9
+ targetKind : ConfigMap # <4>
Original file line number Diff line number Diff line change @@ -12,10 +12,12 @@ A TrustStore looks like this:
12
12
include::example$truststore-tls.yaml[]
13
13
----
14
14
<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` .
17
19
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.
19
21
It can then either be mounted into a Pod or retrieved and used from outside of Kubernetes.
20
22
21
23
NOTE: Make sure to have a procedure for updating the retrieved certificates.
You can’t perform that action at this time.
0 commit comments