1.2 KiB
1.2 KiB
Required Kubernetes secrets
Base manifests and the Hetzner single-node overlay both expect secrets to be supplied out-of-band. The Hetzner overlay generates unrip/unrip-secrets, forgejo/forgejo-secrets, and registry/registry-secrets from local files.
Required secrets
unrip/unrip-secretsNEAR_INTENTS_API_KEY
forgejo/forgejo-secretsroot_urldomainrunner_registration_token
registry/registry-secretshtpasswd
Overlay-driven generation
The deploy/k8s/overlays/hetzner-single-node overlay can generate these from local files via secretGenerator.
Example workflow:
cp deploy/k8s/overlays/hetzner-single-node/secrets/unrip.env.example deploy/k8s/overlays/hetzner-single-node/secrets/unrip.env
cp deploy/k8s/overlays/hetzner-single-node/secrets/forgejo.env.example deploy/k8s/overlays/hetzner-single-node/secrets/forgejo.env
cp deploy/k8s/overlays/hetzner-single-node/secrets/registry.htpasswd.example deploy/k8s/overlays/hetzner-single-node/secrets/registry.htpasswd
kubectl apply -k deploy/k8s/overlays/hetzner-single-node
For future projects, follow the same convention with project-specific secret names in project-specific namespaces.
Do not commit populated secret files.