Merge branch 'main' into ai-assistant-changelog

Author: mjang

.github/CODEOWNERS

@@ -15,19 +15,31 @@
 
 # DocOps Writers
 *                           @nginx/nginx-docs
+
 # DocOps Engineers
 .github/*                   @nginx/docs-engineering
-# NGINX Plus
-content/nginx/*             @nginx/plus-docs-approvers
+
 # NGINX Agent
-content/nginx/nms/agent/*   @nginx/agent-docs-approvers
-# NGINX One
-content/nginx-one/*         @nginx/one-docs-approvers
-# NGINX Instance Manager
-content/nms/nim/*           @nginx/nim-docs-approvers
-content/nim/*               @nginx/nim-docs-approvers
+content/nginx/nms/agent/*   @nginx/nginx-agent 
+
+# NGINX App Protect DoS
+content/nap-dos/*           @nginx/dos-docs-approvers
+
 # NGINX App Protect WAF
 content/nap-waf/*           @nginx/nap-docs-approvers
 data/nap-waf/*              @nginx/nap-docs-approvers
-# NGINX App Protect DoS
-content/nap-dos/*           @nginx/dos-docs-approvers
+
+# NGINX Gateway Fabric
+content/ngf/*               @nginx/nginx-gateway-fabric
+content/includes/ngf/*      @nginx/nginx-gateway-fabric
+
+# NGINX Instance Manager
+content/nms/nim/*           @nginx/nim-docs-approvers
+content/nim/*               @nginx/nim-docs-approvers
+
+# NGINX Plus
+content/nginx/*             @nginx/plus-docs-approvers
+
+# NGINX One
+content/nginx-one/*         @nginx/one-docs-approvers
+

.github/pull_request_template.md

@@ -21,15 +21,15 @@ Closes #ISSUE
 
 Before merging a pull request, run through this checklist and mark each as complete.
 
-- [] I have read the [contributing guidelines](/CONTRIBUTING.md)
-- [] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)
-- [] I have ensured that documentation content adheres to [the style guide](/templates/style-guide.md)
-- [] If the change involves potentially sensitive changes, I have assessed the possible impact
-- [] If applicable, I have added tests that prove my fix is effective or that my feature works
-- [] If applicable, I have checked that any relevant tests pass after adding my changes
-- [] I have updated any relevant documentation ([`README.md`](/README.md) and [`CHANGELOG.md`](/CHANGELOG.md))
-- [] I have rebased my branch onto main
-- [] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork
+- [ ] I have read the [contributing guidelines](/CONTRIBUTING.md)
+- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)
+- [ ] I have ensured that documentation content adheres to [the style guide](/templates/style-guide.md)
+- [ ] If the change involves potentially sensitive changes, I have assessed the possible impact
+- [ ] If applicable, I have added tests that prove my fix is effective or that my feature works
+- [ ] If applicable, I have checked that any relevant tests pass after adding my changes
+- [ ] I have updated any relevant documentation ([`README.md`](/README.md) and [`CHANGELOG.md`](/CHANGELOG.md))
+- [ ] I have rebased my branch onto main
+- [ ] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork
 
 Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation.
 

.github/workflows/fossa.yml

@@ -25,6 +25,6 @@ jobs:
         uses: actions/checkout@85e6279cec87321a52edac9c87bce653a07cf6c2 # v4.2.2
 
       - name: Scan
-        uses: fossas/fossa-action@09bcf127dc0ccb4b5a023f6f906728878e8610ba # v1.4.0
+        uses: fossas/fossa-action@93a52ecf7c3ac7eb40f5de77fd69b1a19524de94 # v1.5.0
         with:
           api-key: ${{ secrets.FOSSA_TOKEN }}

.github/workflows/ossf_scorecard.yml

@@ -56,6 +56,6 @@ jobs:
 
       # Upload the results to GitHub's code scanning dashboard.
       - name: Upload SARIF results to code scanning
-        uses: github/codeql-action/upload-sarif@b6a472f63d85b9c78a3ac5e89422239fc15e9b3c # v3.28.1
+        uses: github/codeql-action/upload-sarif@f6091c0113d1dcf9b98e269ee48e8a7e51b7bdd4 # v3.28.5
         with:
           sarif_file: results.sarif

.github/workflows/stale.yml

@@ -18,7 +18,7 @@ jobs:
       pull-requests: write  # for actions/stale to close stale PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v9.0.0
+      - uses: actions/stale@v9.1.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           stale-issue-message: 'This issue is stale because it has been open for 90 days with no activity. Remove the stale label or add a comment to keep it open. If you do not take action, this will be closed in 10 days.'

content/ngf/how-to/_index.md

@@ -1,4 +1,5 @@
 ---
 title: "How-to guides"
+url: /nginx-gateway-fabric/how-to/
 weight: 400
 ---

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

@@ -1,4 +1,5 @@
 ---
 title: "Monitoring and troubleshooting"
+url: /nginx-gateway-fabric/how-to/monitoring/
 weight: 300
 ---

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/_index.md

@@ -1,4 +1,5 @@
 ---
 title: "Traffic management"
+url: /nginx-gateway-fabric/how-to/traffic-management/
 weight: 100
 ---

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.