Migrate Tailscale Ingresses to shared ProxyGroup for per-Ingress tagging
The legacy per-Ingress StatefulSet proxy model silently ignores the tailscale.com/tags annotation, so tag:flyio-target was never applied to docs/loki/prometheus — breaking the restricted ACL. This adds a ProxyGroup (type: Ingress, 2 replicas) and annotates all 12 Ingresses with tailscale.com/proxy-group: "ingress" to enable per-Ingress tag overrides and restore connectivity. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
e152b1b071
commit
756f2dff13
15 changed files with 24 additions and 1 deletions
|
|
@ -1 +1 @@
|
|||
Restrict fly.io proxy ACLs to dedicated `tag:flyio-target` endpoints instead of broad `tag:k8s` and `tag:homelab` grants. Alloy now pushes logs/metrics directly to Loki and Prometheus via Tailscale Ingress, bypassing Caddy.
|
||||
Restrict fly.io proxy ACLs to dedicated `tag:flyio-target` endpoints instead of broad `tag:k8s` and `tag:homelab` grants. Alloy now pushes logs/metrics directly to Loki and Prometheus via Tailscale Ingress, bypassing Caddy. Migrate all Tailscale Ingresses to a shared ProxyGroup to enable per-Ingress tag overrides (`tag:flyio-target` on docs, loki, prometheus).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue