Open ramaraochavali opened 6 years ago
Curious: what would be the TTL of such a cache?
xrefing https://github.com/envoyproxy/envoy/issues/868 which is about HTTP caching, but would introduce the existence of a physical cache
@jmarantz since #868 is solved now, what does it take to implement this?
Is there any progress or plans?
Curious: what would be the TTL of such a cache?
I think TTL should be configurable. :)
It must be prioritized.
How can you use an external authenticator without a cache. This reduces performance too much.
It would be great to have this. Ext auth without a cache is practically unusable.
Use Case : I am setting up Envoy Gateway in our infra and wanted to centralise auth. Currently each of our services has a local cache. If I shift to authorisation using envoy, both request count on central auth service would increase and latency of req would also increase.
A configuration where users can enable/disable caching and also mention a ttl for the cache if enabled would be helpful.
Currently External Auth filter reaches out to configured external auth service for every request. This is a performance penalty. It should support some level of caching so that it does not go to external auth for every request