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: deploy/helm/secret-operator/crds/crds.yaml
+59Lines changed: 59 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -218,6 +218,15 @@ spec:
218
218
description: The Secret objects are located in the same namespace as the Pod object. Should be used for Secrets that are provisioned by the application administrator.
219
219
type: object
220
220
type: object
221
+
trustStoreConfigMapName:
222
+
description: |-
223
+
Name of a ConfigMap that contains the information required to validate against this SecretClass.
224
+
225
+
Resolved relative to `search_namespace`.
226
+
227
+
Required to request a TrustStore for this SecretClass.
228
+
nullable: true
229
+
type: string
221
230
required:
222
231
- searchNamespace
223
232
type: object
@@ -346,3 +355,53 @@ spec:
346
355
served: true
347
356
storage: true
348
357
subresources: {}
358
+
---
359
+
apiVersion: apiextensions.k8s.io/v1
360
+
kind: CustomResourceDefinition
361
+
metadata:
362
+
name: truststores.secrets.stackable.tech
363
+
annotations:
364
+
helm.sh/resource-policy: keep
365
+
spec:
366
+
group: secrets.stackable.tech
367
+
names:
368
+
categories: []
369
+
kind: TrustStore
370
+
plural: truststores
371
+
shortNames: []
372
+
singular: truststore
373
+
scope: Namespaced
374
+
versions:
375
+
- additionalPrinterColumns: []
376
+
name: v1alpha1
377
+
schema:
378
+
openAPIV3Schema:
379
+
description: Auto-generated derived type for TrustStoreSpec via `CustomResource`
380
+
properties:
381
+
spec:
382
+
description: |-
383
+
A [TrustStore](https://docs.stackable.tech/home/nightly/secret-operator/truststore) requests information about how to validate secrets issued by a [SecretClass](https://docs.stackable.tech/home/nightly/secret-operator/secretclass).
384
+
385
+
The requested information is written to a ConfigMap with the same name as the TrustStore.
386
+
properties:
387
+
format:
388
+
description: The [format](https://docs.stackable.tech/home/nightly/secret-operator/secretclass#format) that the data should be converted into.
389
+
enum:
390
+
- tls-pem
391
+
- tls-pkcs12
392
+
- kerberos
393
+
nullable: true
394
+
type: string
395
+
secretClassName:
396
+
description: The name of the SecretClass that the request concerns.
:description: A TrustStore in Kubernetes retrieves the trust anchors from a SecretClass.
3
+
4
+
A _TrustStore_ is a Kubernetes resource that can be used to request the trust anchor information (such as the TLS certificate authorities) from a xref:secretclass.adoc[].
5
+
6
+
This can be used to access a protected service from other services that do not require their own certificates (or from clients running outside of Kubernetes).
7
+
8
+
A TrustStore looks like this:
9
+
10
+
[source,yaml]
11
+
----
12
+
include::example$truststore-tls.yaml[]
13
+
----
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]
17
+
18
+
This will create a ConfigMap named `truststore-pem` containing a `ca.crt` with the trust root certificates.
19
+
It can then either be mounted into a Pod or retrieved and used from outside of Kubernetes.
20
+
21
+
NOTE: Make sure to have a procedure for updating the retrieved certificates.
22
+
The Secret Operator will automatically rotate the xref:secretclass.adoc#backend-autotls[autoTls] certificate authority as needed, but all trust roots will require some form of update occasionally.
0 commit comments