mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-12 02:15:01 +00:00
rosstimothy
5dd08bd2e2
Caching has become an integral part in functionality provided by teleport. Allowing users to disable the cache was never something that was a recomended configuration - it was predominately used as a stopgap to address an outage. However, over time the cache has become more stable and the need to bypass it should never arise. Additionally, this toggle causes several architectural difficulties that increase complexity and maintainability of teleport. By always enforcing that the cache is on, we can eventually separate the gRPC, backend, and caching layers - a frequent developer experience nightmare. Moving to a world where the cache is always guaranteed to be present and available we will be able to remove layers of abstraction and increase performance. We do still honor `teleport.cache.max_backoff`. While it was tempting to remove all teleport.cache knobs, it seemed that still allowing users to control the backoff interval could alleviate any caching related issues that lead to or are contributing to an outage. This seemed rather important to still offer now that the ability to disable caching no longer exists.