Is it possible to switch Kong caching to use Redis instead of memory - use a single cache for multiple instances of Kong, multiple nodes?
Our use case is that we have Kong deployed in Kubernetes on 6 pods and we would like to cache all resources only once and not per pod. One solution I see would be using a single Redis in-memory DB with failover to internal memory (if Redis appears to be down). Does anyone have any experience with that?
The most problematic part for us is rate-limiting plugin as we have it set to
policy=cluster (the behaviour we want) and it causes some bigger latencies as it accesses the DB constantly. I know we could use Redis there but afaik, we would have to pass the redis arguments always - on every creation of rate-limiting - it seems we cannot default to our custom deployment of redis and make redis the default policy instead of cluster.