stack/kustomizations/digitalocean
Ryan Heywood 1b6e5156f4
re-encrypt to drgrove's key
2024-01-11 15:56:53 -05:00
..
cloud-controller-manager k/digitalocean: place resources in vpc-id 2023-05-13 01:31:07 -04:00
csi-driver k/digitalocean: rename CSI drivers (breaking) 2023-06-08 21:55:26 -04:00
scripts docs: add steps to rebuild kustomization secrets 2023-05-16 22:06:13 -04:00
README.md recreate cluster 2023-05-17 01:02:04 -04:00
digitalocean-config.enc.yaml re-encrypt to drgrove's key 2024-01-11 15:56:53 -05:00
kustomization.yaml k/digitalocean: add a Certificate for snapshot validation webhook 2023-05-16 03:44:24 -04:00
secret-generator.yaml k/digitalocean: place resources in vpc-id 2023-05-13 01:31:07 -04:00

README.md

Secrets

DigitalOcean's CNI and CCM, as well as a few other separate Kustomizations, require a DigitalOcean token and a VPC id. This can be generated by running:

sh kustomizations/digitalocean/scripts/generate-digitalocean-token-secret.sh | sops --encrypt --encrypted-regex='^(data|stringData)$' --input-type=yaml --output-type=yaml /dev/stdin > kustomizations/digitalocean/digitalocean-config.enc.yaml