CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: clarification on default TCP ports (#1878)

Browse Source
This commit is contained in:
Joey Freeland authored and GitHub committed 2022-03-30 09:36:30 -07:00
1 parent d2602584ab
commit 15a6ffeb6b
2 files changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/configuration/listener/tcp.mdx
+1 -1
View File
@@ -189,7 +189,7 @@ listener "tcp" {
listener "tcp" {
purpose = "cluster"
address = "10.0.0.5:9200"
address = "10.0.0.5:9201"
}
```
website/content/docs/installing/high-availability.mdx
+2 -2
View File
@@ -13,9 +13,9 @@ Installing Boundary as a high availability service requires certain infrastructu
The following ports should be available:
- Clients must have access to the Controller's port (default 9200)
- Clients must have access to the Controller's `api` port (default 9200)
- Clients must have access to the Worker's port (default 9202)
- Workers must have access to the Controller's port (default 9201)
- Workers must have access to the Controller's `cluster` port (default 9201)
- Workers must have a route and port access to the hosts defined within the system in order to provide connectivity
## Architecture