Use secrets from an .env file rather than from individual files
As a follow-up of this review of !405. We should better use secrets from an .env file so we have all secrets/values in one file instead of cluttering a directory with multiple files.
I propose the following workflow for OAS installation, after installation part 1 (k3s + flux2 via ansible) succeeded:
- copy over a new pre-populated
.env
file containing a env var boilerplate like this:
ADMIN_EMAIL='admin@oas.example.org'
DOMAIN='oas.example.org'
…
cp install/.env.example clusters/varac-test/.env
cp install/kustomization.yaml clusters/varac-test
cp install/
cd clusters/varac-test
- Customize it:
vim .env
- Source it
source .env
- Apply the kustomization
kubectl apply -k .
Edited by Varac