Skip to content

Commit fa9461b

Browse files
Aias00claude
andcommitted
release-notes: correct scope of named RateLimitRule to local and global
The release note for #9151 previously mentioned only the global rate-limit metric key, but the change to irRuleName affects both the local and global rate-limit rule keys. Update the note to reflect the actual scope. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: liuhy <liuhongyu@apache.org>
1 parent 7945422 commit fa9461b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
Added an optional `name` field to `RateLimitRule` in BackendTrafficPolicy. When set, the global rate-limit metric key uses the provided name (e.g. `<policy-namespace>/<policy-name>/rule/<name>`) instead of the array index (e.g. `.../rule/0`), making rate-limit metrics easier to identify and stable across rule reordering. Unset `name` preserves the existing index-based behavior.
1+
Added an optional `name` field to `RateLimitRule` in BackendTrafficPolicy. When set, both local and global rate-limit rule keys use the provided name (e.g. `<policy-namespace>/<policy-name>/rule/<name>`) instead of the array index (e.g. `.../rule/0`), making rate-limit rule keys and metrics easier to identify and stable across rule reordering. Unset `name` preserves the existing index-based behavior.

0 commit comments

Comments
 (0)