Merge branch 'main' into nap-release-5.5

Author: ADubhlaoich

content/ngf/how-to/monitoring/prometheus.md

@@ -73,7 +73,7 @@ In the Grafana UI menu, go to `Connections` then `Data sources`. Add your Promet
 
 Download the following sample dashboard and Import as a new Dashboard in the Grafana UI.
 
-- {{< download "grafana-dashboard.json" "ngf-grafana-dashboard.json" >}}
+- {{< download "ngf/grafana-dashboard.json" "ngf-grafana-dashboard.json" >}}
 
 ---
 

content/ngf/how-to/traffic-management/routing-traffic-to-your-app.md

@@ -33,7 +33,7 @@ You can route traffic to your Kubernetes applications using the Gateway API and
 
 The application we are going to use in this guide is a simple **coffee** application comprised of one service and two pods:
 
-{{<img src="img/route-all-traffic-app.png" alt="This image shows a single 'coffee' Service connecting to two 'coffee' Pods.">}}
+{{<img src="ngf/img/route-all-traffic-app.png" alt="This image shows a single 'coffee' Service connecting to two 'coffee' Pods.">}}
 
 Using this architecture, the **coffee** application is not accessible outside the cluster. We want to expose this application on the hostname "cafe.example.com" so that clients outside the cluster can access it.
 
@@ -108,15 +108,15 @@ service/coffee       ClusterIP   198.51.100.1     <none>        80/TCP    77s
 
 To route traffic to the **coffee** application, we will create a gateway and HTTPRoute. The following diagram shows the configuration we are creating in the next step:
 
-{{<img src="img/route-all-traffic-config.png" alt="">}}
+{{<img src="ngf/img/route-all-traffic-config.png" alt="">}}
 
 We need a gateway to create an entry point for HTTP traffic coming into the cluster. The **cafe** gateway we are going to create will open an entry point to the cluster on port 80 for HTTP traffic.
 
 To route HTTP traffic from the gateway to the **coffee** service, we need to create an HTTPRoute named **coffee** and attach it to the gateway. This HTTPRoute will have a single routing rule that routes all traffic to the hostname "cafe.example.com" from the gateway to the **coffee** service.
 
 Once NGINX Gateway Fabric processes the **cafe** gateway and **coffee** HTTPRoute, it will configure its data plane (NGINX) to route all HTTP requests sent to "cafe.example.com" to the pods that the **coffee** service targets:
 
-{{<img src="img/route-all-traffic-flow.png" alt="Traffic Flow">}}
+{{<img src="ngf/img/route-all-traffic-flow.png" alt="Traffic Flow">}}
 
 The **coffee** service is omitted from the diagram above because the NGINX Gateway Fabric routes directly to the pods that the **coffee** service targets.
 

content/ngf/how-to/traffic-security/integrating-cert-manager.md

@@ -32,7 +32,7 @@ Follow the steps in this guide to:
 
 ## Secure traffic using Let's Encrypt and cert-manager
 
-{{<img src="img/cert-manager-gateway-workflow.png" alt="cert-manager ACME challenge and certificate management with Gateway API">}}
+{{<img src="ngf/img/cert-manager-gateway-workflow.png" alt="cert-manager ACME challenge and certificate management with Gateway API">}}
 
 The diagram above shows a simplified representation of the cert-manager ACME challenge and certificate issuance process using Gateway API. Please note that not all of the kubernetes objects created in this process are represented in this diagram.