fluxcd
/
kustomize-controller
mirror of https://github.com/fluxcd/kustomize-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: Clarify `.spec.decryption.secretRef` usage 

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2024-09-13 09:17:52 +03:00
parent 1e9d28b251
commit 46f6cf80f4
No known key found for this signature in database
GPG Key ID: 3299AEB0E4085BAF
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/spec/v1/kustomizations.md
View File

@ -739,12 +739,13 @@ Secret, encrypting the `metadata`, `kind` or `apiVersion` fields is not supporte
An easy way to do this is by appending `--encrypted-regex '^(data|stringData)$'`
to your `sops --encrypt` command.
It has two required fields:
It has two fields:
- `.provider`: The secrets decryption provider to be used. This field is required and
the only supported value is `sops`.
- `.secretRef.name`: The name of the secret that contains the keys to be used for
decryption.
- `.provider`: The secrets decryption provider to be used. The only supported
value at the moment is `sops`.
decryption. This field can be omitted when using the
[global decryption](#controller-global-decryption) option.
```yaml
---