Replaces fromEntities: world on allow-syslog-world-ingress with the CIDR groups of the networks that actually send syslog:
net-management: switches and APs
net-iot: SLZB coordinators, edge-1/edge-2
net-k8s-ingress: the UDM, which sources from 10.2.47.1
Senders taken from Hubble flows to the alloy-syslog pod and from the Loki host label over 7 days. The LB is ETP=Local, so client addresses reach the pod. Server-side dry-run passes.
Replaces `fromEntities: world` on `allow-syslog-world-ingress` with the CIDR groups of the networks that actually send syslog:
- `net-management`: switches and APs
- `net-iot`: SLZB coordinators, edge-1/edge-2
- `net-k8s-ingress`: the UDM, which sources from 10.2.47.1
Senders taken from Hubble flows to the alloy-syslog pod and from the Loki `host` label over 7 days. The LB is ETP=Local, so client addresses reach the pod. Server-side dry-run passes.
Refs S28-19
🤖 Generated with [Claude Code](https://claude.com/claude-code)
alloy-syslog accepted syslog from any world source. Senders seen in
Hubble and Loki over the last 7 days: switches and APs on Management,
SLZB coordinators and edge hosts on IoT, and the UDM, which sources from
its k8s-ingress address 10.2.47.1. The LB is ETP=Local, so those client
addresses reach the pod.
Refs S28-19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Replaces
fromEntities: worldonallow-syslog-world-ingresswith the CIDR groups of the networks that actually send syslog:net-management: switches and APsnet-iot: SLZB coordinators, edge-1/edge-2net-k8s-ingress: the UDM, which sources from 10.2.47.1Senders taken from Hubble flows to the alloy-syslog pod and from the Loki
hostlabel over 7 days. The LB is ETP=Local, so client addresses reach the pod. Server-side dry-run passes.Refs S28-19
🤖 Generated with Claude Code