Skip to content

Label edge NetworkServices with their load balancer and listener #888

Closed

Description

@0xmc

Summary

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:

networking.datumapis.com/nlb-name: <load balancer name>
networking.datumapis.com/nlb-listener: <listener name>

The namespace already identifies the project, so no project label is needed. Label keys are a suggestion. Reuse an existing owner label if one fits.

Acceptance criteria

  • Each edge NetworkService for a load balancer listener names that load balancer and listener in its labels.
  • Renaming or replacing a listener updates the labels on the next reconcile.
  • NetworkServices the operator doesn't own are left unchanged.

Activity

  1. self-assigned this
    on Nov 17, 2026
  2. added a commit that references this issue on Nov 17, 2026
    08a4e9c
  3. 0xmc commented on Nov 17, 2026

    @0xmc
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions