-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Document high availability cache #1057
Comments
I am removing it from 2.3 milestone. IMO such documentation does not belong to product docs, because it does not affect how Teleport should be used. This is probably good for "contributor documentation" or maybe for a "Teleport under the hood" blog post. Leaving it open though, this is good stuff we should be documenting, if not for users but for devs/contributors. |
I was thinking it might be a good fit here: https://github.com/gravitational/teleport/blob/master/docs/2.0/architecture.md |
Closing this due to inactivity. Things have changed a lot since 2017 :-) |
* Refactor `DocumentGateway` * Update protobuf files * Do not hide port input on reconnect * Update port of gateway connection when doc gets updated Co-authored-by: Rafał Cieślak <[email protected]> Co-authored-by: Grzegorz Zdunek <[email protected]>
Problem
In #853, we introduced a cache that can be used to make Teleport more resilient in the face of failures. However, we don't have any documentation on how to enable or disable this and we also don't have any architectural diagrams that explain how this new HA concept works.
Proposed Solution
The text was updated successfully, but these errors were encountered: