mirror of
https://github.com/luxfi/monitoring.git
synced 2026-10-30 15:24:48 +00:00
zeekayandHanzo Dev
7e35c626c1
ghcr.io/luxfi/monitoring is an `internal` package with NO linked repository, so it is not pullable anonymously and not every org credential is authorised for it. The Deployment declared no imagePullSecrets at all, so the pod never started: 8,394 backoff events over 31h, during which the validator-health alerting this repo exists to provide was blind. It must be `ghcr-secret`, NOT `ghcr-luxfi`. Verified against the registry from inside the cluster — ghcr-secret gets 200 on the v0.1.1 manifest, ghcr-luxfi gets 403. ghcr-luxfi is used by 53 other deployments in that cluster and works for luxfi/node, so "it pulls other luxfi images" would have been the wrong inference; the package's own ACL is what matters. Verified after applying: pod 1/1 Running, /metrics 200 serving 211 lux_ series. Context for whoever reads this next: the same 31h window contained a REAL incident the alerting correctly detected and nobody received — the Hanzo mainnet chain is halted at height 1218 with 3 of 5 validators against a 4-of-5 quorum. Separately, alertmanager's SLACK_WEBHOOK_URL points at http://alert-sink.hanzo.svc (the internal logging pod), so every page is delivered to a log line rather than a human. Co-authored-by: Hanzo Dev <[email protected]>