add tenant name

This commit is contained in:
Angel Nunez Mencias 2025-04-10 13:47:54 +02:00
parent 3090bae888
commit 0af35b308b
Signed by: angel.nunez
SSH key fingerprint: SHA256:z1nFAg1v1AfbhEHrgBetByUJUwziv2R2f4VyN75opcg
3 changed files with 1 additions and 1 deletions

24
vars/demo/.sops.yaml Normal file
View file

@ -0,0 +1,24 @@
---
# This example uses YAML anchors which allows reuse of multiple keys
# without having to repeat yourself.
# Also see https://github.com/Mic92/dotfiles/blob/master/nixos/.sops.yaml
# for a more complex example.
keys:
age:
- &tenant_age_key age1zr4gpsus63fl4555j357dyn04lhgljyrhmgqwy0rfc9j5hqwseaspdykvf
creation_rules:
- path_regex: .+secret(\.sops)?\.ya?ml
input_type: yaml
encrypted_regex: ^(data|stringData)$
key_groups:
- age: &key_groups
- *tenant_age_key
- path_regex: .+secret(\.sops)?\.env
input_type: env
key_groups:
- age: *key_groups
stores:
yaml:
indent: 2

11
vars/demo/README.md Normal file
View file

@ -0,0 +1,11 @@
# Settings and Secrets
Add here settings that depend on the tenant name. This is needed when you
include this git ${REPO_NAME} into multiple tenants. You need to ensure this
folder is called the same way as the kvant tenant you got.
You can add Config Maps and secrets to this folder. The secrets should be
encripted using SOPS (see
[WIKI](https://git.kvant.cloud/phoenix/tenant-tpl/wiki/Tenant--Wiki)). Please
do not forget adding your own key to the [.sops.yaml](.sops.yaml) before
encrypting your secrets if you want to be able to edit them afterwards.

7
vars/demo/example.yaml Normal file
View file

@ -0,0 +1,7 @@
---
apiVersion: v1
kind: ConfigMap
metadata:
name: example-vars
data:
EXAMPLE: foo