move the default upstream timeout page to global-timeouts (#1688)

* move the default upstream timeout page to global-timeouts

* prettier

* update link

* fix heading style

Author: calebdoxsey

content/docs/internals/connection.mdx

@@ -70,7 +70,7 @@ Different timeouts apply at various stages of the connection lifecycle:
 
 - **Request timeout**: This timeout applies to the total time a request can take, which includes connection establishment, request forwarding, processing at the upstream service, and response forwarding. If a complete response is not received within the set timeout, Pomerium will return an error to the client. This timeout can be configured via the [`timeout_write`](/docs/reference/global-timeouts) parameter. It may need adjustment, for instance, when handling large uploads.
 
-- **Upstream timeout**: This timeout applies to the time a request takes to travel from Pomerium to the upstream service and back. It can be configured per-route via the [`timeout`](/docs/reference/routes/timeouts#route-timeout) parameter and is considered part of the request timeout. By default, it aligns with the global [`default_upstream_timeout`](/docs/reference/default-upstream-timeout) setting.
+- **Upstream timeout**: This timeout applies to the time a request takes to travel from Pomerium to the upstream service and back. It can be configured per-route via the [`timeout`](/docs/reference/routes/timeouts#route-timeout) parameter and is considered part of the request timeout. By default, it aligns with the global [`default_upstream_timeout`](/docs/reference/global-timeouts#default-upstream-timeout) setting.
 
 ![Example of HTTP request lifecycle and timeout settings](./img/timeouts-http-request/timeouts-http-diagram.png)
 

content/docs/reference/default-upstream-timeout.mdx

@@ -164,4 +164,42 @@ timeouts:
 </TabItem>
 </Tabs>
 
+## Default Upstream Timeout
+
+**Default Upstream Timeout** is the default timeout applied to a proxied route when no `timeout` key is specified by the policy.
+
+### How to configure
+
+<Tabs>
+<TabItem value="Core" label="Core">
+
+| **Config file keys** | **Environment variables** | **Type** | **Default** |
+| :-- | :-- | :-- | :-- |
+| `default_upstream_timeout` | `DEFAULT_UPSTREAM_TIMEOUT` | [Go Duration] string | `30s` |
+
+### Examples
+
+```yaml
+default_upstream_timeout: 30s
+```
+
+```bash
+DEFAULT_UPSTREAM_TIMEOUT=1h45m
+```
+
+</TabItem>
+<TabItem value="Enterprise" label="Enterprise">
+
+Set **Default Upstream Timeout** in the Console:
+
+![Enterprise Console with default timeout setting](./img/timeouts/default-upstream-timeout.png)
+
+</TabItem>
+<TabItem value="Kubernetes" label="Kubernetes">
+
+Kubernetes does not support `default_upstream_timeout`
+
+</TabItem>
+</Tabs>
+
 [go duration]: https://golang.org/pkg/time/#Duration.String

content/docs/reference/global-timeouts.mdx

@@ -434,6 +434,7 @@ https://0-20-0.docs.pomerium.com/category/guides https://0-20-0.docs.pomerium.co
 /docs/reference/routes/set-authorization-header /docs/reference/routes/headers#set-authorization-header
 
 # Timeouts
+/docs/reference/default-upstream-timeout /docs/reference/global-timeouts#default-upstream-timeout
 /docs/reference/routes/websocket-connections /docs/reference/routes/timeouts#websocket-connections
 /docs/reference/routes/spdy /docs/reference/routes/timeouts#spdy
 /docs/reference/routes/route-timeout /docs/reference/routes/timeouts#route-timeout