You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/content/docs/configuration/controller.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ description will be read.
79
79
`cluster` purpose.
80
80
81
81
You can use this attribute if you want to put a load balancer in front of multiple Boundary controllers to ensure that the workers know the addresses of the controllers to perform client-side load balancing.
82
-
For example, you could have a TCP load balancer that points to any of your controller's `cluster` listener for the worker's initial ingress.
82
+
For example, you could have a TCP load balancer that points to a controller's `cluster` listener for the worker's initial ingress.
83
83
Then the controller gives the worker the `public_cluster_addr` and the worker updates its client-side load balancing configuration to connect to the set of cluster addresses.
84
84
85
85
This setting is also especially useful for cloud environments that do not
0 commit comments