Add note about policy limitaton

Author: Kate Osborn

site/content/how-to/monitoring/tracing.md

@@ -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 HTTPRoutes that have [HTTPRouteMatches](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch) with `headers`, `params`, or `method` matchers defined.
+{{< /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.

site/content/how-to/traffic-management/client-settings.md

@@ -28,6 +28,10 @@ Settings applied to an HTTPRoute or GRPCRoute take precedence over settings appl
 
 This guide will show you how to use the `ClientSettingsPolicy` API to configure the client max body size for your applications.
 
+{{< important >}}
+The `ClientSettingsPolicy` API does not work with HTTPRoutes that have [HTTPRouteMatches](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteMatch) with `headers`, `params`, or `method` matchers defined.
+{{< /important >}}
+
 ## Setup
 
 - [Install]({{< relref "/installation/" >}}) NGINX Gateway Fabric.