-
Notifications
You must be signed in to change notification settings - Fork 0
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
Breakdown Architecture into Guide pages #11
base: andyet/docs-v4.1
Are you sure you want to change the base?
Conversation
This commit fixes goroutine leak - whenever a leaf cluster disconnects from the root cluster, the caching access point cache update loop has to be closed as well.
Fixed anti-pattern use of /var/run as the PID dir
* First draft updating Trusted Cluster
…nal#2956) * Info for backup and Restore * Include information about path in storage.
* Add Dynamo stream configuration * Update to NEW_IMAGE as per docs
Signed-off-by: Antoine Bardoux <[email protected]>
* PV template to use Values.persistence.accessMode * use apps/v1 * expose replica count for modification
Added diagrams and got this to a place where the Architecture Section (formerly known as Concepts) replaces the previous Architecture Guide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this is officially "ready for review" yet but I was browsing through and thought I'd add some comments. Looks great overall.
@webvictim thanks for the review and catching some typos! |
* Removed hardcoded aws access_keys in favour of customers using IAM and aws credentials.
gravitational#3073) * Clarified IAM docs section + added policy example * Added IAM for DynamoDB to docs
Overview of Changes
Motivation
This PR introduces a new section called "Concepts". This change attempts to address a couple of issue I saw in the previous docs version.
In this PR I attempted to pull out the key concepts of Teleport and write explainer docs on each of them. I also attempted to eliminate the need for repetitive explanations of concepts in the step-by-step guide. Guides can now focus on practical tasks and provide minimal inline definitions. They will reference users to concept docs for detailed explanations of terms and ideas.
Possible Problems
As I was writing I found that it was hard to describe each concept alone without duplicating some information between docs. For example the Proxy Service relies heavily on the Auth Service so you can't really discuss one without the other. As these are refined it will be challenging to describe each concept clearly while minimizing duplicate information.
Graphics
I still need to create or revise graphics for most of these pages. This can be done in a later PR so non-blocking. It would be nice to use some of the existing graphical elements to preserve a consistent feel, but if that's not possible I can start from scratch on lucidchart.