From 639df2ea9d8eb85f888ba8598de5c025a883f1a9 Mon Sep 17 00:00:00 2001 From: Mile Date: Sat, 13 Jul 2024 22:25:20 +0200 Subject: [PATCH] adding missing overview in documentation --- .../how-to/traffic-management/routing-traffic-to-your-app.md | 2 +- .../how-to/traffic-management/securing-backend-traffic.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site/content/how-to/traffic-management/routing-traffic-to-your-app.md b/site/content/how-to/traffic-management/routing-traffic-to-your-app.md index cf310df780..7d4b6bf08c 100644 --- a/site/content/how-to/traffic-management/routing-traffic-to-your-app.md +++ b/site/content/how-to/traffic-management/routing-traffic-to-your-app.md @@ -129,7 +129,7 @@ spec: protocol: HTTP EOF ``` - +## Overview This gateway is associated with the 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]({{< relref "/reference/cli-help.md#static-mode" >}}). We specify a [listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Listener) on the gateway to open an entry point on the cluster. In this case, since the coffee application accepts HTTP requests, we create an HTTP listener, named **http**, that listens on port 80. diff --git a/site/content/how-to/traffic-management/securing-backend-traffic.md b/site/content/how-to/traffic-management/securing-backend-traffic.md index edb0b1eaa3..0bb387647a 100644 --- a/site/content/how-to/traffic-management/securing-backend-traffic.md +++ b/site/content/how-to/traffic-management/securing-backend-traffic.md @@ -105,7 +105,7 @@ data: EOF ``` - +## Overview This will create the **secure-app** service and a deployment, as well as a Secret containing the certificate and key that will be used by the backend application to decrypt the HTTPS traffic. Note that the application is configured to accept HTTPS traffic only. Run the following command to verify the resources were created: ```shell