Merge branch 'revamp-spec-summary-table' of https://github.com/ChisomUma/ngixdocsopensourcecontribution into revamp-spec-summary-table

Author: ChisomUma

.github/workflows/coveo.yml

@@ -84,7 +84,7 @@ jobs:
 
       - name: Retrieve secrets from Keyvault
         id: keyvault
-        uses: azure/cli@089eac9d8cc39f5d003e94f8b65efc51076c9cbd
+        uses: azure/cli@9f7ce6f37c31b777ec6c6b6d1dfe7db79f497956
         with:
           inlineScript: |
             secrets_get=(productionHostname previewHostname resourceGroupName cdnProfileName cdnName accountName)

.github/workflows/linkchecker.yml

@@ -84,7 +84,7 @@ jobs:
       - name: Retrieve secrets from Keyvault
         if: env.isProduction != 'true'
         id: keyvault
-        uses: azure/cli@089eac9d8cc39f5d003e94f8b65efc51076c9cbd
+        uses: azure/cli@9f7ce6f37c31b777ec6c6b6d1dfe7db79f497956
         with:
           inlineScript: |
             secrets_get=(frontdoorUsername frontdoorPassword)

.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@192325c86100d080feab897ff886c34abd4c83a3 # v3.29.5
+        uses: github/codeql-action/upload-sarif@3599b3baa15b485a2e49ef411a7a4bb2452e7f93 # v3.29.5
         with:
           sarif_file: results.sarif

content/includes/agent/installation/update-container.md

@@ -10,7 +10,7 @@ To migrate NGINX Agent containers, we provide a script to convert NGINX Agent v2
 To upgrade the configuration, you can follow this example:
 
 ```shell
-wget https://raw.githubusercontent.com/nginx/agent/refs/heads/v3/scripts/packages/upgrade-agent-config.sh
+wget https://raw.githubusercontent.com/nginx/agent/refs/heads/main/scripts/packages/upgrade-agent-config.sh
 ./upgrade-agent-config.sh --v2-config-file=./nginx-agent-v2.conf --v3-config-file=nginx-agent-v3.conf
 ```
 

content/ngf/traffic-management/basic-routing.md

@@ -39,7 +39,7 @@ graph TB
 
 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.
 
-Install NGINX Gateway Fabric and create two Gateway API resources: a [gateway](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Gateway) and an [HTTPRoute](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRoute).
+Install NGINX Gateway Fabric and create two Gateway API resources: a [gateway](https://gateway-api.sigs.k8s.io/reference/spec/#gateway) and an [HTTPRoute](https://gateway-api.sigs.k8s.io/reference/spec/#httproute).
 
 Using these resources we will configure a simple routing rule to match all HTTP traffic with the hostname "cafe.example.com" and route it to the **coffee** service.
 
@@ -240,10 +240,10 @@ In a production environment, you should have a DNS record for the external IP ad
 
 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#controller" >}}).
 
-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.
+We specify a [listener](https://gateway-api.sigs.k8s.io/reference/spec/#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.
 
 By default, Gateways only allow routes (such as HTTPRoutes) to attach if they are in the same namespace as the Gateway. If you want to change this behavior, you can set
-the [**allowedRoutes**](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.AllowedRoutes) field.
+the [**allowedRoutes**](https://gateway-api.sigs.k8s.io/reference/spec/#allowedroutes) field.
 
 Next you will create the HTTPRoute by copying and pasting the following into your terminal:
 
@@ -269,11 +269,11 @@ spec:
 EOF
 ```
 
-To attach the **coffee** HTTPRoute to the **cafe** Gateway, we specify the Gateway name in the [**parentRefs**](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.CommonRouteSpec) field. The attachment will succeed if the hostnames and protocol in the HTTPRoute are allowed by at least one of the Gateway's listeners.
+To attach the **coffee** HTTPRoute to the **cafe** Gateway, we specify the Gateway name in the [**parentRefs**](https://gateway-api.sigs.k8s.io/reference/spec/#parentreference) field. The attachment will succeed if the hostnames and protocol in the HTTPRoute are allowed by at least one of the Gateway's listeners.
 
-The [**hostnames**](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec) field allows you to list the hostnames that the HTTPRoute matches. In this case, incoming requests handled by the **http** listener with the HTTP host header "cafe.example.com" will match this HTTPRoute and will be routed according to the rules in the spec.
+The [**hostnames**](https://gateway-api.sigs.k8s.io/reference/spec/#hostname) field allows you to list the hostnames that the HTTPRoute matches. In this case, incoming requests handled by the **http** listener with the HTTP host header "cafe.example.com" will match this HTTPRoute and will be routed according to the rules in the spec.
 
-The [**rules**](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule) field defines routing rules for the HTTPRoute. A rule is selected if the request satisfies one of the rule's **matches**. To forward traffic for all paths to the coffee service we specify a match with the PathPrefix "/" and target the coffee service using the **backendRef** field.
+The [**rules**](https://gateway-api.sigs.k8s.io/reference/spec/#httprouterule) field defines routing rules for the HTTPRoute. A rule is selected if the request satisfies one of the rule's **matches**. To forward traffic for all paths to the coffee service we specify a match with the PathPrefix "/" and target the coffee service using the **backendRef** field.
 
 ---
 

content/nginx/technical-specs.md

@@ -27,14 +27,15 @@ Dynamic modules are supported on the [same distributions as NGINX Plus](#support
 |--------------|------------|-------|---------|---------------|------------|---------------|
 | **AlmaLinux** | ❌ | ❌ | ✓ | ✓ | ✓ | ✓ |
 | **Alpine Linux 3.17 & 3.18** | ❌ | ✓ | ✓ | ❌ | ❌ | ✓ |
-| **Alpine Linux 3.19** | ✓ (x86_64 only) | ✓ | ✓ | ❌ | ❌ | ✓ |
+| **Alpine Linux 3.19, 3.20, 3.21, 3.22 | ✓ (x86_64 only) | ✓ | ✓ | ❌ | ❌ | ✓ |
 | **Amazon Linux 2** | ❌ | ✓ | ❌ | ❌ | ✓ | ❌ |
 | **Amazon Linux 2023** | ✓ (x86_64 only) | ❌ | ✓ | ❌ | ✓ | ✓ |
 | **Debian 11 & 12** | ✓ (x86_64 only) | ✓ | ✓ | ✓ | ✓ | ✓ |
 | **FreeBSD** | ❌ | ❌ | ✓ | ❌ | ❌ | ✓ |
-| **Oracle Linux 8** | ✓ (x86_64 only) |  (Oracle Linux: ❌) | ✓ | ✓ | ✓ | ✓ |
-| **RHEL 8 & 9** | ✓ (x86_64 only) |  (RHEL: ❌)| ✓ | ✓ | ✓ | ✓ |
-| **Rocky Linux 8** | ❌ |  (Rocky Linux 8.0+: ❌)| ✓ | ✓ | ✓ | ✓ |
+| **Oracle Linux 8** | ✓ (x86_64 only) |  ❌ | ✓ | ✓ | ✓ | ✓ |
+| **RHEL 8 & 9** | ✓ (x86_64 only) | ❌ | ✓ | ✓ | ✓ | ✓ |
+| **RHEL 10** | ✓ | ❌ | ✓ | ✓ | ✓ | ✓ |
+| **Rocky Linux 8** | ❌ |  ❌ | ✓ | ✓ | ✓ | ✓ |
 | **Rocky Linux 9** | ✓ (x86_64 only) | ❌ | ✓ | ✓ | ✓ | ✓ |
 | **SLES** | ❌ | ✓ | ✓ | ✓ | ✓ | ❌ |
 | **Ubuntu 20.04** | ❌ | ✓ | ✓ | ✓ | ✓ | ✓ |

content/nic/configuration/virtualserver-and-virtualserverroute-resources.md

@@ -51,7 +51,7 @@ spec:
   - path: ~ ^/decaf/.*\\.jpg$
     action:
       pass: coffee
-  - path: = /green/tea
+  - path: =/green/tea
     action:
       pass: tea
 ```