Ben Vincent
9882bbe5d5
Why: - The cert-manager v1.20.2 controller crashloops: strict decoding of its ControllerConfiguration rejects the unknown field `acmeDNS01`, so /var/cert-manager/config/config.yaml fails to load and the controller never starts; the stuck rollout leaves only the old pod serving. - PR #337 placed the DNS-01 recursive-nameserver settings under `acmeDNS01`, but the field in the controller.config.cert-manager.io/v1alpha1 schema is `acmeDNS01Config`. How: - Rename the config block `acmeDNS01` to `acmeDNS01Config`, keeping `recursiveNameservers` (8.8.8.8:53, 1.1.1.1:53) and `recursiveNameserversOnly: true` so DNS-01 resolution and self-checks still use the public DNS view for the split-horizon delegation.
argocd-apps docs
Operational notes for the manifests in this repo.
| Doc | What it covers |
|---|---|
| cnpg-backups.md | How CNPG Postgres backups (WAL archiving + nightly base backups) to Ceph RGW are configured. |
| cnpg-restore.md | Restoring a CNPG cluster: full recovery, point-in-time recovery, cutover, and gotchas. |
| authentik-rancher-sso.md | Manual runtime step to point Rancher's OIDC auth at the canonical identity.unkin.net issuer and trust the internal CA. |
| gitea-migration.md | Staged cutover of the git.unkin.net forge from the Puppet VM to the gitea namespace. |
| ca-rotation.md | Rolling the internal unkin.net PKI CA (vault-ca-cert): what Reloader restarts automatically vs. manual/CNPG restarts. |