-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding Which ratelimit Package to Use #1760
Comments
looks like the API lives here https://github.com/envoyproxy/ratelimit/blob/main/api/ratelimit/config/ratelimit/v3/rls_conf.proto and its generated go files live here so the proto API will need to be sprinkled with tags from https://github.com/bufbuild/protoc-gen-validate and then we'd need to run this https://github.com/bufbuild/protoc-gen-validate#go what I can't find is, where is the |
@phlax @mattklein123 @renuka-fernando |
We have not automated generating pb files. I've created an issue [1] for that but couldn't get it done. |
We can't use 'github.com/envoyproxy/go-control-plane/envoy/config/ratelimit/v3'. This is the API for Envoy and RateLimit Service communication. 'github.com/envoyproxy/go-control-plane/ratelimit/config/ratelimit/v3' is for RateLimit Service and RateLimit xDS service communication. |
@renuka-fernando Thanks. |
It looks like I don't have the necessary permissions to reopen the issue envoyproxy/go-control-plane#646. cc: @phlax |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Description: Currently, 'internal/xds/translator/ratelimit.go' utilizes 'github.com/envoyproxy/go-control-plane/ratelimit/config/ratelimit/v3'. 'ratelimit.RateLimitConfig' does not have the ValidateAll() function, as a result, we cannot validate the resource. We need to understand why we don't use 'github.com/envoyproxy/go-control-plane/envoy/config/ratelimit/v3'.
[optional Relevant Links:] You may find more context at #1662 (comment)
The text was updated successfully, but these errors were encountered: