unkin-agent
f268c4d9ba
ghp serves metrics over HTTPS (TLS configured globally), but the liveness/readiness probes used the default HTTP scheme, so the kubelet probe hit an HTTPS-server error and pods never went Ready. Set scheme: HTTPS on both probes (kubelet does not verify the probe cert). The VMServiceScrape targets that same HTTPS endpoint, so set scheme: https with tlsConfig.insecureSkipVerify (internal-CA cert, pod-IP target not in the cert SANs); otherwise VM scraping of ghp fails. - deployment.yaml: liveness+readiness probes scheme HTTP -> HTTPS - vmservicescrape.yaml: scheme https + tlsConfig.insecureSkipVerify
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. |