Ben Vincent
a5f3b18e86
The puppet MASTER is the singleton CA/master: a second master, even transiently during a rolling update, races on CA/cert signing and shared state. It was previously driven by an HPA (minReplicas 2, maxReplicas 5) with a RollingUpdate strategy, so 2-5 masters could coexist and a rollout would briefly run old+new masters against the same shared CA PVC. - Set puppetserver-master replicas to 1 and strategy to Recreate so the old master always terminates before a new one starts. - Remove the puppetserver-masters-autoscaler HPA (and its kustomization entry) that forced 2-5 master replicas. - Refresh the master VPA note to reflect the pinned-singleton, no-HPA state. Claude-Session: https://claude.ai/code/session_01JUoARVdmhxKQHyyyp1pxeT
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. |