From 1ea5d4d2e30f033233a60755c9c8973962e46103 Mon Sep 17 00:00:00 2001 From: Stefan Prodan Date: Thu, 8 Apr 2021 12:11:01 +0300 Subject: [PATCH] Remove sourceignore from SOPS guide No longer needed due to https://github.com/fluxcd/source-controller/pull/329 Signed-off-by: Stefan Prodan --- docs/guides/mozilla-sops.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/guides/mozilla-sops.md b/docs/guides/mozilla-sops.md index 6877b7d8..4f3449a6 100644 --- a/docs/guides/mozilla-sops.md +++ b/docs/guides/mozilla-sops.md @@ -143,23 +143,13 @@ Multiple directories can use separate SOPS configs. Contributors using the `sops` CLI to create and encrypt files won't have to worry about specifying the proper key for the target cluster or namespace. -`encrypted_regex` helps encrypt the the proper `data` and `stringData` fields for Secrets. +`encrypted_regex` helps encrypt the `data` and `stringData` fields for Secrets. You may wish to add other fields if you are encrypting other types of Objects. !!! hint Note that you should encrypt only the `data` or `stringData` section. Encrypting the Kubernetes secret metadata, kind or apiVersion is not supported by kustomize-controller. -Ignore all `.sops.yaml` files in a [`.sourceignore`](../components/source/gitrepositories#excluding-files) -file at the root of your repo. - -```sh -touch .sourceignore -echo '**/.sops.yaml' >> .sourceignore -``` - -You can now commit your SOPS config. - ## Encrypt secrets Generate a Kubernetes secret manifest with kubectl: