Skip to content

Commit

Permalink
Update compat tables and fix link
Browse files Browse the repository at this point in the history
  • Loading branch information
kate-osborn committed Jun 7, 2024
1 parent 4cb7040 commit 50dc040
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 13 deletions.
2 changes: 1 addition & 1 deletion site/content/how-to/traffic-management/client-settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The settings in `ClientSettingsPolicy` correspond to the following NGINX directi
When applied to a Gateway, the settings specified in the `ClientSettingsPolicy` affect all HTTPRoutes and GRPCRoutes attached to the Gateway. This allows Cluster Operators to set defaults for all applications using the Gateway.

When applied to an HTTPRoute or GRPCRoute, the settings in the `ClientSettingsPolicy` affect only the route they are applied to. This allows Application Developers to set values for their applications based on their application's behavior or requirements.
Settings applied to an HTTPRoute or GRPCRoute take precedence over settings applied to a Gateway. See the [custom policies]({{< relref "/overview/custom-policies.md>}}) documentation for more information on policies.
Settings applied to an HTTPRoute or GRPCRoute take precedence over settings applied to a Gateway. See the [custom policies]({{< relref "overview/custom-policies.md" >}}) document for more information on policies.

This guide will show you how to use the `ClientSettingsPolicy` API to configure the client max body size for your applications.

Expand Down
24 changes: 12 additions & 12 deletions site/content/overview/gateway-api-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ docs: "DOCS-1412"
{{< bootstrap-table "table table-striped table-bordered" >}}
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| ------------------------------------- | ------------------- | ---------------------- | ------------------------------------- | ----------- |
| [GatewayClass](#gatewayclass) | Supported | Not supported | Not supported | v1 |
| [Gateway](#gateway) | Supported | Not supported | Not supported | v1 |
| [GatewayClass](#gatewayclass) | Supported | Not supported | Supported | v1 |
| [Gateway](#gateway) | Supported | Partially supported | Not supported | v1 |
| [HTTPRoute](#httproute) | Supported | Partially supported | Not supported | v1 |
| [ReferenceGrant](#referencegrant) | Supported | N/A | Not supported | v1beta1 |
| [GRPCRoute](#grpcroute) | Partially Supported | Not supported | Not supported | v1 |
| [GRPCRoute](#grpcroute) | Partially Supported | Partially supported | Not supported | v1 |
| [TLSRoute](#tlsroute) | Not supported | Not supported | Not supported | N/A |
| [TCPRoute](#tcproute) | Not supported | Not supported | Not supported | N/A |
| [UDPRoute](#udproute) | Not supported | Not supported | Not supported | N/A |
Expand Down Expand Up @@ -48,9 +48,9 @@ For a description of each field, visit the [Gateway API documentation](https://g
### GatewayClass

{{< bootstrap-table "table table-striped table-bordered" >}}
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| ------------ | ------------------ | ---------------------- | ------------------------------------- | ----------- |
| GatewayClass | Supported | Not supported | Not supported | v1 |
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level| API Version |
| ------------ | ------------------ | ---------------------- | ----------------------------------- | ----------- |
| GatewayClass | Supported | Not supported | Supported | v1 |
{{< /bootstrap-table >}}

NGINX Gateway Fabric supports a single GatewayClass resource configured with the `--gatewayclass` flag of the [static-mode]({{< relref "/reference/cli-help.md#static-mode">}}) command.
Expand All @@ -76,9 +76,9 @@ NGINX Gateway Fabric supports a single GatewayClass resource configured with the
### Gateway

{{< bootstrap-table "table table-striped table-bordered" >}}
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| -------- | ------------------ | ---------------------- | ------------------------------------- | ----------- |
| Gateway | Supported | Not supported | Not supported | v1 |
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| -------- | ------------------ | -----------------------------| ------------------------------------- | ----------- |
| Gateway | Supported | Partially supported | Not supported | v1 |
{{< /bootstrap-table >}}

NGINX Gateway Fabric supports a single Gateway resource. The Gateway resource must reference NGINX Gateway Fabric's corresponding GatewayClass.
Expand Down Expand Up @@ -185,9 +185,9 @@ See the [static-mode]({{< relref "/reference/cli-help.md#static-mode">}}) comman
### GRPCRoute

{{< bootstrap-table "table table-striped table-bordered" >}}
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| --------- | ------------------- | ---------------------- | ------------------------------------- | ----------- |
| GRPCRoute | Supported | Not supported | Not supported | v1 |
| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
| --------- | ------------------- | -----------------------------| ------------------------------------- | ----------- |
| GRPCRoute | Supported | Partially supported | Not supported | v1 |
{{< /bootstrap-table >}}

**Fields**:
Expand Down

0 comments on commit 50dc040

Please sign in to comment.