Description:
BackendTrafficPolicy currently restricts spec.rateLimit.*.rules[].clientSelectors[].headers to a maximum of 16 items:
|
Headers []HeaderMatch `json:"headers,omitempty"` |
For complex policies, this limit is too restrictive.
In our use case, a single rate-limit rule needs to match more than 16 headers (for multi-tenant routing, client metadata, and policy segmentation), and the CRD validation blocks the policy.
Current behavior
Applying a policy with >16 header match entries fails validation with a must have at most 16 items error.
Proposal
Increase RateLimitSelectCondition.headers MaxItems from 16 to a higher value (for example 64 or 128), preferably in incremental steps if needed.
Can this be increased?
[optional Relevant Links:]
Any extra documentation required to understand the issue.
Description:
BackendTrafficPolicy currently restricts spec.rateLimit.*.rules[].clientSelectors[].headers to a maximum of 16 items:
gateway/api/v1alpha1/ratelimit_types.go
Line 232 in 8fa767a
For complex policies, this limit is too restrictive.
In our use case, a single rate-limit rule needs to match more than 16 headers (for multi-tenant routing, client metadata, and policy segmentation), and the CRD validation blocks the policy.
Current behavior
Applying a policy with >16 header match entries fails validation with a must have at most 16 items error.
Proposal
Increase RateLimitSelectCondition.headers MaxItems from 16 to a higher value (for example 64 or 128), preferably in incremental steps if needed.
Can this be increased?
[optional Relevant Links:]