-
|
Hello, I'm looking for a way to use my pod that can expose both http and grpc (based on rls.proto) as a middleware for auth/rate_limit service. Unfortunately, documentation on net is all over the place usually referencing CRDs that do not exist anymore. This is especially annoying with AIs all over the place that are just misleading (including AskAI in gateway.envoyproxy.io/docs/) Is there any doc/example that can be used for this usa case? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Ext Auth: https://gateway.envoyproxy.io/docs/tasks/security/ext-auth/ Global Ratelimit: https://gateway.envoyproxy.io/docs/tasks/traffic/global-rate-limit/ if you want to bring your own ratelimit service and program the ratelimit filter in envoy directly: https://gateway.envoyproxy.io/docs/tasks/extensibility/envoy-patch-policy/ |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @arkodg. Combination of first two might work for my case. I'm also looking in https://gateway.envoyproxy.io/v1.6/tasks/extensibility/ext-proc/ and example code That looks as the most flexible way to auth and rate limit in a single place. |
Beta Was this translation helpful? Give feedback.
Ext Auth: https://gateway.envoyproxy.io/docs/tasks/security/ext-auth/
Global Ratelimit: https://gateway.envoyproxy.io/docs/tasks/traffic/global-rate-limit/
if you want to bring your own ratelimit service and program the ratelimit filter in envoy directly: https://gateway.envoyproxy.io/docs/tasks/extensibility/envoy-patch-policy/