Skip to content

Commit e26ca30

Browse files
committed
feat: Remove additional unnecessary shell instructions
1 parent 729c169 commit e26ca30

File tree

3 files changed

+14
-21
lines changed

3 files changed

+14
-21
lines changed

content/ngf/traffic-management/tls-passthrough.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,12 @@ In this guide, we will show how to configure TLS passthrough for your applicatio
2828
## Before you begin
2929

3030
- [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric with experimental features enabled.
31-
- Save the public IP address and port of NGINX Gateway Fabric into shell variables:
3231

33-
```text
34-
GW_IP=XXX.YYY.ZZZ.III
35-
GW_TLS_PORT=<port number>
36-
```
32+
{{< note >}}
3733

38-
{{< 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 >}}
34+
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.
35+
36+
{{< /note >}}
3937

4038
---
4139

content/ngf/traffic-management/upstream-settings.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -35,20 +35,17 @@ For all the possible configuration options for `UpstreamSettingsPolicy`, see the
3535
## Before you begin
3636

3737
- [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric.
38-
- Save the public IP address and port of NGINX Gateway Fabric into shell variables:
39-
40-
```text
41-
GW_IP=XXX.YYY.ZZZ.III
42-
GW_PORT=<port number>
43-
```
44-
45-
- Lookup the name of the NGINX Gateway Fabric pod and save into shell variable:
38+
- Check the name of the NGINX Gateway Fabric pod and save into a shell variable:
4639

4740
```text
4841
NGF_POD_NAME=<NGF Pod>
4942
```
5043

51-
{{< 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 >}}
44+
{{< note >}}
45+
46+
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.
47+
48+
{{< /note >}}
5249

5350
---
5451

content/ngf/traffic-security/securing-backend-traffic.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,12 @@ In this guide, we will show how to specify the TLS configuration of the connecti
2828
## Before you begin
2929

3030
- [Install]({{< ref "/ngf/install/" >}}) NGINX Gateway Fabric with experimental features enabled.
31-
- Save the public IP address and port of NGINX Gateway Fabric into shell variables:
3231

33-
```text
34-
GW_IP=XXX.YYY.ZZZ.III
35-
GW_PORT=<port number>
36-
```
32+
{{< note >}}
3733

38-
{{< 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 >}}
34+
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.
35+
36+
{{< /note >}}
3937

4038
---
4139

0 commit comments

Comments
 (0)