From f32daa4258744814806f7d2e6b14695a249ca4b9 Mon Sep 17 00:00:00 2001 From: Lorenzo Corallo Date: Mon, 2 Nov 2026 20:18:18 +0100 Subject: [PATCH] fix(backend): allow Uptime Kuma through the network policy --- apps/backend/network-policy.yaml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/apps/backend/network-policy.yaml b/apps/backend/network-policy.yaml index 3e2519c..f460e35 100644 --- a/apps/backend/network-policy.yaml +++ b/apps/backend/network-policy.yaml @@ -1,6 +1,7 @@ # Only the in-cluster callers may reach the backend (RFC v3 ยง12): the admin # dashboard and the website (tRPC, esign agent proxy), the Telegram bot (tRPC -# and its socket) and the IdP (access-changed events on /internal/events). +# and its socket), the IdP (access-changed events on /internal/events) and +# Uptime Kuma (health monitoring). # Nothing reaches it from outside the cluster since the Ingress was removed. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy @@ -38,6 +39,12 @@ spec: podSelector: matchLabels: app: auth + - namespaceSelector: + matchLabels: + kubernetes.io/metadata.name: uptime-kuma + podSelector: + matchLabels: + app: uptime-kuma ports: - port: 3000 protocol: TCP