Skip to content

Conversation

@simu
Copy link
Member

@simu simu commented Nov 11, 2025

This PR introduces a new field policy_labels for entries in egress_ip_ranges. In contrast to field bgp_policy_labels, providing labels in the new field doesn't modify the behavior of the policy generation.

Checklist

  • The PR has a meaningful title. It will be used to auto-generate the
    changelog.
    The PR has a meaningful description that sums up the change. It will be
    linked in the changelog.
  • PR contains a single logical change (to build a better changelog).
  • Update the documentation.
  • Categorize the PR by adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency
    as they show up in the changelog.

@simu simu added the enhancement New feature or request label Nov 11, 2025
@simu simu force-pushed the feat/egress-ip-range-cidr branch 2 times, most recently from 52be249 to 68cd898 Compare November 11, 2025 12:28
@simu simu force-pushed the feat/namespace-egress-policy-labels branch 2 times, most recently from 2e18f6a to 40a46da Compare November 11, 2025 14:40
Base automatically changed from feat/egress-ip-range-cidr to master November 12, 2025 14:17
…ss policies

This commit introduces a new field `policy_labels` for entries in
`egress_ip_ranges`. In contrast to field `bgp_policy_labels`, providing
labels in the new field doesn't modify the behavior of the policy
generation.
@simu simu force-pushed the feat/namespace-egress-policy-labels branch from 40a46da to 26346d0 Compare November 12, 2025 14:22
@simu simu requested a review from a team November 12, 2025 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants