You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Label edge NetworkServices with their load balancer and listener #888
Consumers can't attribute a network load balancer's traffic counters to the load balancer that owns them. The gateway labels its per-listener counters with VIP, port and protocol only, and the edge NetworkService the operator writes is named after its cell intent and carries no labels, so nothing on the edge says which load balancer or listener it serves.
Adding owner labels lets kube-state-metrics export a mapping from VIP, port and protocol to load balancer and listener, which a metrics pipeline can join to the counters.
Proposed change
Set these labels on every NetworkService the cell programming controller writes, from the intent's parent and listener, and keep them in step on update:
The fix in #913 writes annotations rather than labels: networking.datumapis.com/nlb-name and networking.datumapis.com/nlb-listener. A load balancer name can run to 253 characters and a label value allows 63, so a label would fail the write. Read "labels" in the acceptance criteria as these annotations.
Activity
feat: Annotate edge NetworkServices with their NLB
0xmc commentedon Nov 17, 2026
The fix in #913 writes annotations rather than labels:
networking.datumapis.com/nlb-nameandnetworking.datumapis.com/nlb-listener. A load balancer name can run to 253 characters and a label value allows 63, so a label would fail the write. Read "labels" in the acceptance criteria as these annotations.