unkin-agent
693f541840
go-cache-plugin serve binds 127.0.0.1 only, so a Service cannot reach it directly and CI/developer builds have no way to use the S3-backed cache. - Run go-cache-plugin serve against the gocache RGW bucket, path-style, with an explicit region to skip the GetBucketLocation probe - Add an nginx sidecar stream-proxying 9090 to the loopback plugin port - Restrict the listener to the workstation and pod CIDRs: GOCACHEPROG is unauthenticated and a poisoned entry runs in every consuming build - Stage the cache on an emptyDir; loss costs a repopulate from S3
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. |