Merge branch 'release-1.3' into docs/release-1.3.0

Author: lucacome

.github/workflows/conformance.yml

@@ -80,7 +80,7 @@ jobs:
         uses: goreleaser/goreleaser-action@286f3b13b1b49da4ac219696163fb8c1c93e1200 # v6.0.0
         with:
           version: latest
-          args: build --snapshot --clean
+          args: build --single-target --snapshot --clean
         env:
           TELEMETRY_ENDPOINT: "" # disables sending telemetry
           TELEMETRY_ENDPOINT_INSECURE: "false"

.github/workflows/functional.yml

@@ -68,7 +68,7 @@ jobs:
         uses: goreleaser/goreleaser-action@286f3b13b1b49da4ac219696163fb8c1c93e1200 # v6.0.0
         with:
           version: latest
-          args: build --snapshot --clean
+          args: build --single-target --snapshot --clean
         env:
           TELEMETRY_ENDPOINT: otel-collector-opentelemetry-collector.collector.svc.cluster.local:4317
           TELEMETRY_ENDPOINT_INSECURE: "true"
@@ -98,6 +98,14 @@ jobs:
             NGINX_CONF_DIR=internal/mode/static/nginx/conf
             BUILD_AGENT=gha
 
+      - name: Install cloud-provider-kind
+        run: |
+          curl -fsSL -O https://github.com/kubernetes-sigs/cloud-provider-kind/releases/download/v0.2.0/cloud-provider-kind_0.2.0_linux_amd64.tar.gz
+          tar -xvf cloud-provider-kind_0.2.0_linux_amd64.tar.gz
+
+      - name: Run cloud-provider-kind
+        run: ./cloud-provider-kind & > cloud-provider-kind.log 2>&1
+
       - name: Deploy Kubernetes
         id: k8s
         run: |
@@ -108,12 +116,12 @@ jobs:
         run: |
           ngf_prefix=ghcr.io/nginxinc/nginx-gateway-fabric
           ngf_tag=${{ steps.ngf-meta.outputs.version }}
-          make test${{ inputs.image == 'plus' && '-with-plus' || ''}} PREFIX=${ngf_prefix} TAG=${ngf_tag} GINKGO_LABEL=telemetry
+          make test${{ inputs.image == 'plus' && '-with-plus' || ''}} PREFIX=${ngf_prefix} TAG=${ngf_tag} GINKGO_LABEL=telemetry GW_SERVICE_TYPE=LoadBalancer
         working-directory: ./tests
 
       - name: Run functional tests
         run: |
           ngf_prefix=ghcr.io/nginxinc/nginx-gateway-fabric
           ngf_tag=${{ steps.ngf-meta.outputs.version }}
-          make test${{ inputs.image == 'plus' && '-with-plus' || ''}} PREFIX=${ngf_prefix} TAG=${ngf_tag}
+          make test${{ inputs.image == 'plus' && '-with-plus' || ''}} PREFIX=${ngf_prefix} TAG=${ngf_tag} GW_SERVICE_TYPE=LoadBalancer
         working-directory: ./tests

build/Dockerfile

@@ -11,7 +11,7 @@ RUN make build
 
 FROM golang:1.22 as ca-certs-provider
 
-FROM alpine:3.19 as capabilizer
+FROM alpine:3.20 as capabilizer
 RUN apk add --no-cache libcap
 
 FROM capabilizer as local-capabilizer

build/Dockerfile.nginxplus

@@ -5,7 +5,7 @@ FROM scratch as nginx-files
 ADD --link --chown=101:1001 https://cs.nginx.com/static/keys/nginx_signing.rsa.pub nginx_signing.rsa.pub
 
 
-FROM alpine:3.19
+FROM alpine:3.20
 
 ARG NGINX_PLUS_VERSION=R32
 ARG NJS_DIR

examples/client-settings-policy/README.md

@@ -1,3 +1,3 @@
 # Client Settings Policy
 
-This directory contains YAML files of ClientSettingsPolicies.
+This directory contains the YAML files used in the [ClientSettingsPolicy](https://docs.nginx.com/nginx-gateway-fabric/how-to/traffic-management/client-settings/) guide.

examples/client-settings-policy/cafe.yaml renamed to examples/client-settings-policy/app.yaml

@@ -1,19 +1,11 @@
 apiVersion: gateway.nginx.org/v1alpha1
 kind: ClientSettingsPolicy
 metadata:
-  name: gw
-  namespace: default
+  name: gateway-client-settings
 spec:
   targetRef:
     group: gateway.networking.k8s.io
     kind: Gateway
     name: gateway
   body:
-    maxSize: 10m
-    timeout: 30s
-  keepAlive:
-    requests: 100
-    time: 5s
-    timeout:
-      server: 2s
-      header: 1s
+    maxSize: "50" # sizes without a unit are bytes.

examples/client-settings-policy/csp-grpcroute.yaml

@@ -9,7 +9,3 @@ spec:
     port: 80
     protocol: HTTP
     hostname: "*.example.com"
-  - name: http2
-    port: 8080
-    protocol: HTTP
-    hostname: "*.example.org"

examples/client-settings-policy/csp-httproutes.yaml

@@ -0,0 +1,11 @@
+apiVersion: gateway.nginx.org/v1alpha1
+kind: ClientSettingsPolicy
+metadata:
+  name: grpc-client-settings
+spec:
+  targetRef:
+    group: gateway.networking.k8s.io
+    kind: GRPCRoute
+    name: my-grpc-route
+  body:
+    maxSize: "75" # sizes without a unit are bytes.

examples/client-settings-policy/csp-gateway.yaml renamed to examples/client-settings-policy/gateway-client-settings.yaml

@@ -0,0 +1,11 @@
+apiVersion: gateway.nginx.org/v1alpha1
+kind: ClientSettingsPolicy
+metadata:
+  name: tea-client-settings
+spec:
+  targetRef:
+    group: gateway.networking.k8s.io
+    kind: HTTPRoute
+    name: tea
+  body:
+    maxSize: "75" # sizes without a unit are bytes.

examples/client-settings-policy/gateway.yaml

@@ -13,6 +13,10 @@ NGINX Gateway Fabric supports tracing using [OpenTelemetry](https://opentelemetr
 
 This guide explains how to enable tracing on HTTPRoutes using NGINX Gateway Fabric. It uses the OpenTelemetry Collector and Jaeger to process and collect the traces.
 
+{{< important >}}
+Tracing cannot be enabled for [HTTPRoute matches](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch) with `headers`, `params`, or `method` matchers defined. It will be added in a future release.
+{{< /important >}}
+
 ## Install the Collectors
 
 The first step is to install the collectors. NGINX Gateway Fabric will be configured to export to the OpenTelemetry Collector, which is configured to export to Jaeger. This model allows the visualization collector (Jaeger) to be swapped with something else, or to add more collectors without needing to reconfigure NGINX Gateway Fabric. It is also possible to configure NGINX Gateway Fabric to export directly to Jaeger.

examples/client-settings-policy/grpc-client-settings.yaml

@@ -109,3 +109,31 @@ If using NGINX Gateway Fabric with NGINX Plus as the data plane, you will see th
 #### Resolution
 
 To resolve this issue, enable Usage Reporting by following the [Usage Reporting]({{< relref "installation/usage-reporting.md" >}}) guide.
+
+### 413 Request Entity Too Large
+
+#### Description
+
+If you receive the following error:
+
+```text
+<html>
+<head><title>413 Request Entity Too Large</title></head>
+<body>
+<center><h1>413 Request Entity Too Large</h1></center>
+<hr><center>nginx/1.25.5</center>
+</body>
+</html>
+```
+
+Or view the following error message in the NGINX logs:
+
+```text
+2024/05/30 21:48:22 [error] 138#138: *43 client intended to send too large body: 112 bytes, client: 127.0.0.1, server: cafe.example.com, request: "POST /coffee HTTP/1.1", host: "cafe.example.com:8080"
+```
+
+The request body exceeds the [client_max_body_size](https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size).
+
+#### Resolution
+
+You can configure the `client_max_body_size` using the `ClientSettingsPolicy` API. Read the [Client Settings Policy]({{< relref "how-to/traffic-management/client-settings.md" >}}) documentation for more information.