From 8e55c4357a1275a4d43abc81bd5ac65d915c6a0b Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Wed, 22 Apr 2026 21:24:22 +0000 Subject: [PATCH] [poison-fountain] opt ingress out of Uptime Kuma external monitor Deployment is scaled to replicas=0 to silence ExternalAccessDivergence, but the ingress at poison.viktorbarzin.me was still auto-annotated `external-monitor=true` by ingress_factory (dns_type=non-proxied path), so external-monitor-sync kept creating `[External] poison` which probed a backend with no endpoints and flagged DOWN. Setting `external_monitor = false` emits the explicit opt-out annotation; next sync run deleted the orphaned monitor. Co-Authored-By: Claude Opus 4.7 (1M context) --- stacks/poison-fountain/main.tf | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/stacks/poison-fountain/main.tf b/stacks/poison-fountain/main.tf index 639d504f..870a1675 100644 --- a/stacks/poison-fountain/main.tf +++ b/stacks/poison-fountain/main.tf @@ -219,6 +219,10 @@ module "ingress" { skip_default_rate_limit = true exclude_crowdsec = true anti_ai_scraping = false + # Deployment is scaled to 0 (see replicas above). Opt the ingress out of + # Uptime Kuma external monitoring so the sync CronJob deletes the orphaned + # `[External] poison` monitor instead of flapping DOWN. + external_monitor = false extra_annotations = { "gethomepage.dev/enabled" = "true" "gethomepage.dev/name" = "Poison Fountain"