postiz+portal: remove broken alert sources (stale backup CronJob, bogus scrape annotations)

Viktor is getting daily Slack alert noise; these two were the recurring
generators. The postiz-postgres-backup CronJob still dumped from the old
in-namespace postiz-postgresql service that was removed in the CNPG
migration (2026-06-28) — it failed every night at 03:00 and re-fired
BackupCronJobFailed each day. The postiz DB now lives on the shared CNPG
cluster and is already covered by the dbaas per-db dumps, so the CronJob
(and its NFS backup volume) is redundant and removed rather than repaired.

portal-stt/portal-tts advertised prometheus.io scrape annotations that
never worked: the deployed Speaches build 404s /metrics, and openai-edge-tts
has no metrics at all (its annotation pointed at a JSON endpoint, which
fails exposition parsing regardless). Both produced a permanently firing
ScrapeTargetDown. Annotations removed until the apps actually serve metrics.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-07-01 22:35:21 +00:00
parent 5a312563c6
commit 3c476dab32
3 changed files with 6 additions and 121 deletions

View file

@ -184,14 +184,9 @@ resource "kubernetes_service" "portal_tts" {
name = "portal-tts"
namespace = kubernetes_namespace.portal_tts.metadata[0].name
labels = local.labels
annotations = {
# openai-edge-tts has no /metrics; annotation-based scrape kept on a live
# path so the Service stays in the scrape set (Ready-endpoint relabeling
# filters non-Ready pods). /v1/models is the OpenAI model list.
"prometheus.io/scrape" = "true"
"prometheus.io/path" = "/v1/models"
"prometheus.io/port" = "8000"
}
# No scrape annotations: openai-edge-tts exposes no Prometheus metrics, and
# scraping a JSON endpoint (/v1/models) fails exposition parsing anyway ->
# up=0 -> a permanently firing ScrapeTargetDown.
}
spec {
type = "ClusterIP"