opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-10-28 03:19:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update faq.md (#3382)

Browse Source 
fixed grammar for new FAQ on scalability / hardware recommendations
This commit is contained in:
Taylor Wakefield
2020-02-25 15:32:04 -08:00
committed by GitHub
parent 827084f2a1
commit 0ca244ee18
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/4.2/faq.md
+2 -2
View File
@@ -35,7 +35,7 @@ it has been fixed with Teleport 4.0. Once you've upgraded your Teleport Cluste
option `--auth-server` to point to web proxy address (this would be `public_addr` and `web_listen_addr`
in file configuration). As defined in [Adding a node located behind NAT - Teleport Node Tunneling](admin-guide.md#adding-a-node-located-behind-nat)
### What's Teleport scalability and hardware recommendations?
### What are Teleport's scalability and hardware recommendations?
We recommend setting up Teleport with a [High Availability configuration](admin-guide.md#high-availability). Below is our
recommended hardware for the Proxy and Auth server. If you plan to connect more than 10,000 nodes, please
@@ -98,4 +98,4 @@ This allows Teleport Pro to print a warning if users are exceeding the usage lim
of their license. The reporting library code is [on Github](https://github.com/gravitational/reporting).
Reach out to `sales@gravitational.com` if you have questions about the commercial
edition of Teleport.
edition of Teleport.