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: content/docs/reference/grpc.mdx
-37
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,6 @@ Pomerium's gRPC settings apply to internal communication between:
21
21
These settings have no effect on gRPC traffic proxied on a regular Pomerium route.
22
22
23
23
-[gRPC Address](#grpc-address)
24
-
-[gRPC Client DNS RoundRobin](#grpc-client-dns-roundrobin)
25
24
-[gRPC Client Timeout](#grpc-client-timeout)
26
25
-[gRPC Insecure](#grpc-insecure)
27
26
@@ -61,42 +60,6 @@ GRPC_ADDRESS=:8443
61
60
</TabItem>
62
61
</Tabs>
63
62
64
-
## gRPC Client DNS RoundRobin {#grpc-client-dns-roundrobin}
65
-
66
-
**gRPC Client DNS RoundRobin** enables DNS-based round-robin load balancing. This method uses DNS to resolve endpoints and distributes load balancing of _all_ addresses returned by the DNS record client side. **Do not disable** unless you have a specific use case.
67
-
68
-
### How to configure {#how-to-configure-grpc-client-dns-roundrobin}
`grpc_client_dns_roundrobin` is a bootstrap configuration setting and is not configurable in the Console.
91
-
92
-
</TabItem>
93
-
<TabItemvalue="Kubernetes"label="Kubernetes">
94
-
95
-
Kubernetes does not support **gRPC Client DNS RoundRobin**
96
-
97
-
</TabItem>
98
-
</Tabs>
99
-
100
63
## gRPC Client Timeout {#grpc-client-timeout}
101
64
102
65
**gRPC Client Timeout** sets the maximum time before canceling an upstream gRPC request. During transient failures, the proxy will retry upstream servers for this duration. You should leave this high enough to handle backend service restart and rediscovery so that client requests do not fail.
0 commit comments