feat: Move external IP note for NGF beside shell variable instructions

ADubhlaoich · ADubhlaoich · commit 857e3228fedd · 2025-06-03T17:15:07.000+01:00
diff --git a/content/ngf/traffic-management/advanced-routing.md b/content/ngf/traffic-management/advanced-routing.md
@@ -27,8 +27,6 @@ The goal is to create a set of rules that will result in client requests being s
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
 
-{{< 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 >}}
-
 ## Coffee applications
 
 ### Deploy the Coffee applications
@@ -65,12 +63,16 @@ After creating the Gateway resource, NGINX Gateway Fabric will provision an NGIN
 
 Save the public IP address and port of the NGINX Service into shell variables:
 
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   GW_PORT=<port number>
-   ```
+```text
+GW_IP=XXX.YYY.ZZZ.III
+GW_PORT=<port number>
+```
+
+{{< 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 >}}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 >}}
+{{< /note >}}
 
 The [HTTPRoute](https://gateway-api.sigs.k8s.io/api-types/httproute/) is typically deployed by the [application developer](https://gateway-api.sigs.k8s.io/concepts/roles-and-personas/#roles-and-personas_1). To deploy the `coffee` HTTPRoute:
 
diff --git a/content/ngf/traffic-management/client-settings.md b/content/ngf/traffic-management/client-settings.md
@@ -40,8 +40,6 @@ For all the possible configuration options for `ClientSettingsPolicy`, see the [
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
 
-{{< 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 >}}
-
 Create the coffee and tea example applications:
 
 ```yaml
diff --git a/content/ngf/traffic-management/https-termination.md b/content/ngf/traffic-management/https-termination.md
@@ -21,12 +21,6 @@ In this guide, we will show how to configure HTTPS termination for your applicat
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
 
-{{< 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 >}}
-
 ---
 
 ## Set up
@@ -176,7 +170,11 @@ Save the public IP address and ports of the NGINX Service into shell variables:
  GW_HTTPS_PORT=<https port number>
  ```
 
-{{< 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 >}}
+{{< 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 >}}
 
 To create the httproute resources, copy and paste the following into your terminal:
 
diff --git a/content/ngf/traffic-management/mirror.md b/content/ngf/traffic-management/mirror.md
@@ -23,14 +23,6 @@ sent to the **coffee** application will also be sent to the **tea** application
 ## Before you begin
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
-- Save the public IP address and port of NGINX Gateway Fabric into shell variables:
-
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   GW_PORT=<port number>
-   ```
-
-{{< 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 >}}
 
 ---
 
@@ -151,12 +143,16 @@ After creating the Gateway resource, NGINX Gateway Fabric will provision an NGIN
 
 Save the public IP address and port of the NGINX Service into shell variables:
 
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   GW_PORT=<port number>
-   ```
+```text
+GW_IP=XXX.YYY.ZZZ.III
+GW_PORT=<port number>
+```
+
+{{< 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 >}}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 >}}
+{{< /note >}}
 
 Now create an HTTPRoute that defines a RequestMirror filter that copies all requests sent to `/coffee` to be sent to the **coffee** backend and mirrored to the **tea** backend. Use the following command:
 
diff --git a/content/ngf/traffic-management/redirects-and-rewrites.md b/content/ngf/traffic-management/redirects-and-rewrites.md
@@ -25,12 +25,6 @@ To see an example of a redirect using scheme and port, see the [HTTPS Terminatio
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
 
-{{< 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 >}}
-
 ---
 
 ## HTTP rewrites and redirects examples
@@ -73,7 +67,6 @@ In a production environment, you should have a DNS record for the external IP ad
 
 {{< /note >}}
 
-
 ---
 
 ## URLRewrite example
diff --git a/content/ngf/traffic-management/request-response-headers.md b/content/ngf/traffic-management/request-response-headers.md
@@ -21,12 +21,6 @@ This guide describes how to configure the headers application to modify the head
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
 
-{{< 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 >}}
-
 ---
 
 ## HTTP Header Modifiers examples
@@ -63,8 +57,11 @@ GW_IP=XXX.YYY.ZZZ.III
 GW_PORT=<port number>
 ```
 
-{{< 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 >}}
+{{< 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 >}}
 
 ---
 
diff --git a/content/ngf/traffic-management/routing-traffic-to-your-app.md b/content/ngf/traffic-management/routing-traffic-to-your-app.md
@@ -148,7 +148,11 @@ Save the public IP address and port of the NGINX Service into shell variables:
  GW_PORT=<port number>
  ```
 
-{{< 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 >}}
+{{< 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 >}}
 
 This Gateway is associated with NGINX Gateway Fabric through the **gatewayClassName** field. The default installation of NGINX Gateway Fabric creates a GatewayClass with the name **nginx**. NGINX Gateway Fabric will only configure Gateways with a **gatewayClassName** of **nginx** unless you change the name via the `--gatewayclass` [command-line flag]({{< ref "/ngf/reference/cli-help.md#static-mode" >}}).
 
diff --git a/content/ngf/traffic-management/tls-passthrough.md b/content/ngf/traffic-management/tls-passthrough.md
@@ -29,14 +29,6 @@ In this guide, we will show how to configure TLS passthrough for your applicatio
 
 - [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric with experimental features enabled.
 
-{{< 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 >}}
-
----
-
 ## Set up
 
 Create the `secure-app` application by copying and pasting the following block into your terminal:
@@ -178,7 +170,11 @@ GW_IP=XXX.YYY.ZZZ.III
 GW_TLS_PORT=<port number>
 ```
 
-{{< 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 >}}
+{{< 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 >}}
 
 Create a TLSRoute that attaches to the Gateway and routes requests to `app.example.com` to the `secure-app` Service:
 
