Skip to content

NGF: Update Gateway Compatibility Document #540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 20, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions content/ngf/overview/gateway-api-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ NGINX Gateway Fabric supports a single GatewayClass resource configured with the

{{< /bootstrap-table >}}

NGINX Gateway Fabric supports a single Gateway resource. The Gateway resource must reference NGINX Gateway Fabric's corresponding GatewayClass.
NGINX Gateway Fabric supports a multiple Gateway resources. The Gateway resources must reference NGINX Gateway Fabric's corresponding GatewayClass.

See the [static-mode]({{< ref "/ngf/reference/cli-help.md#static-mode">}}) command for more information.

Expand All @@ -100,8 +100,8 @@ See the [static-mode]({{< ref "/ngf/reference/cli-help.md#static-mode">}}) comma
- `gatewayClassName`: Supported.
- `infrastructure`: Partially Supported.
- `parametersRef`: NginxProxy resource supported.
- `labels`: Not supported.
- `annotations`: Not supported.
- `labels`: Supported.
- `annotations`: Supported.
- `listeners`
- `name`: Supported.
- `hostname`: Supported.
Expand All @@ -113,7 +113,6 @@ See the [static-mode]({{< ref "/ngf/reference/cli-help.md#static-mode">}}) comma
- `options`: Not supported.
- `allowedRoutes`: Supported.
- `addresses`: Not supported.
- `infrastructure`: Not supported.
- `backendTLS`: Not supported.
- `status`
- `addresses`: Partially supported (LoadBalancer and Pod IP).
Expand All @@ -124,10 +123,9 @@ See the [static-mode]({{< ref "/ngf/reference/cli-help.md#static-mode">}}) comma
- `Accepted/False/Invalid`
- `Accepted/False/UnsupportedValue`: Custom reason for when a value of a field in a Gateway is invalid or not supported.
- `Accepted/False/GatewayConflict`: Custom reason for when the Gateway is ignored due to a conflicting Gateway.
NGINX Gateway Fabric only supports a single Gateway.
- `Programmed/True/Programmed`
- `Programmed/False/Invalid`
- `Programmed/False/GatewayConflict`: Custom reason for when the Gateway is ignored due to a conflicting Gateway. NGINX Gateway Fabric only supports a single Gateway.
- `Programmed/False/GatewayConflict`: Custom reason for when the Gateway is ignored due to a conflicting Gateway.
- `listeners`
- `name`: Supported.
- `supportedKinds`: Supported.
Expand All @@ -139,7 +137,7 @@ See the [static-mode]({{< ref "/ngf/reference/cli-help.md#static-mode">}}) comma
- `Accepted/False/ProtocolConflict`
- `Accpeted/False/HostnameConflict`
- `Accepted/False/UnsupportedValue`: Custom reason for when a value of a field in a Listener is invalid or not supported.
- `Accepted/False/GatewayConflict`: Custom reason for when the Gateway is ignored due to a conflicting Gateway. NGINX Gateway Fabric only supports a single Gateway.
- `Accepted/False/GatewayConflict`: Custom reason for when the Gateway is ignored due to a conflicting Gateway.
- `Programmed/True/Programmed`
- `Programmed/False/Invalid`
- `ResolvedRefs/True/ResolvedRefs`
Expand Down Expand Up @@ -389,3 +387,5 @@ Custom policies are NGINX Gateway Fabric-specific CRDs (Custom Resource Definiti
While these CRDs are not part of the Gateway API, the mechanism to attach them to Gateway API resources is part of the Gateway API. See the [Policy Attachment documentation](https://gateway-api.sigs.k8s.io/references/policy-attachment/).

See the [custom policies]({{< ref "/ngf/overview/custom-policies.md" >}}) document for more information.

---
Loading