Instead of having a manually prepared secret, use Cloud KMS (as per the previous commits) to decrypt the in-repo secrets and template them into the Secret resource in Kubernetes. Not all of the values are actually secret, it has thus become a bit easier to edit the known hosts, SSH config and such now. |
||
|---|---|---|
| .. | ||
| gemma | ||
| https-cert | ||
| https-lb | ||
| nginx | ||
| nixery | ||
| tazblog | ||
| primary-cluster.yaml | ||