From a1ca27d71850d1971c14db0b2b7ae1f07f428a8d Mon Sep 17 00:00:00 2001 From: Kate Osborn Date: Wed, 8 Jan 2025 09:39:39 -0700 Subject: [PATCH] Add section breaks --- site/content/how-to/traffic-management/upstream-settings.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/site/content/how-to/traffic-management/upstream-settings.md b/site/content/how-to/traffic-management/upstream-settings.md index 3592c58696..c4479d0645 100644 --- a/site/content/how-to/traffic-management/upstream-settings.md +++ b/site/content/how-to/traffic-management/upstream-settings.md @@ -28,6 +28,8 @@ This guide will show you how to use the `UpstreamSettingsPolicy` API to configur For all the possible configuration options for `UpstreamSettingsPolicy`, see the [API reference]({{< relref "reference/api.md" >}}). +--- + ## Before you begin - [Install]({{< relref "/installation/" >}}) NGINX Gateway Fabric. @@ -40,6 +42,8 @@ For all the possible configuration options for `UpstreamSettingsPolicy`, see the {{< note >}}In a production environment, you should have a DNS record for the external IP address that is exposed, and it should refer to the hostname that the gateway will forward for.{{< /note >}} +--- + ## Setup Create the `coffee` and `tea` example applications: @@ -222,6 +226,8 @@ Server address: 10.244.0.9:8080 Server name: tea-76c7c85bbd-cf8nz ``` +--- + ## Configure upstream zone size To set the upstream zone size to 1 megabyte for both the `coffee` and `tea` services, create the following `UpstreamSettingsPolicy`: