Add ListenerSets documentation for NGF

content/ngf/overview/gateway-api-compatibility.md

@@ -93,9 +93,9 @@ See the [controller]({{< ref "/ngf/reference/cli-help.md#controller">}}) command
     - `name`: Supported.
     - `hostname`: Supported.
     - `port`: Supported.
-    - `protocol`: Partially supported. Allowed values: `HTTP`, `HTTPS`.
+    - `protocol`: Supported.
     - `tls`
-      - `mode`: Partially supported. Allowed value: `Terminate`.
+      - `mode`: Supported.
       - `certificateRefs` - The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls`.
       - `options`: The options `nginx.org/ssl-protocols`, `nginx.org/ssl-ciphers` and `nginx.org/ssl-prefer-server-ciphers` are supported. See [ngx_http_ssl_module](https://nginx.org/en/docs/http/ngx_http_ssl_module.html) for more information.
     - `allowedRoutes`: Supported.
@@ -106,9 +106,11 @@ See the [controller]({{< ref "/ngf/reference/cli-help.md#controller">}}) command
     - `frontend`: Not supported.
     - `backend`:
       - `clientCertificateRef`: Supported.
-  - `allowedListeners`: Not supported.
+  - `allowedListeners`: Supported.
+  - `defaultScope`: Not supported.
 - `status`
   - `addresses`: Partially supported (LoadBalancer and ClusterIP).
+  - `attachedListenerSets`: Supported.
   - `conditions`: Supported (Condition/Status/Reason):
     - `Accepted/True/Accepted`
     - `Accepted/True/ListenersNotValid`
@@ -383,6 +385,64 @@ Fields:
 
 {{< call-out "note" >}} If multiple `backendRefs` are defined for a HTTPRoute rule, all the referenced Services *must* have matching BackendTLSPolicy configuration. BackendTLSPolicy configuration is considered to be matching if 1. CACertRefs reference the same ConfigMap, or 2. WellKnownCACerts are the same, and 3. Hostname is the same. {{< /call-out >}}
 
+### ListenerSet
+
+{{< table >}}
+
+| Resource    | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version | API Release Channel |
+|-------------|--------------------|------------------------|---------------------------------------|-------------|---------------------|
+| ListenerSet | Supported          | Supported              | Not supported                         | v1          | Standard            |
+
+{{< /table >}}
+
+**Fields**:
+
+- `spec`
+  - `parentRef`: Supported.
+  - `listeners`
+    - `name`: Supported.
+    - `hostname`: Supported.
+    - `port`: Supported.
+    - `protocol`: Supported.
+    - `tls`
+      - `mode`: Supported.
+      - `certificateRefs` - The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls`.
+      - `options`: The options `nginx.org/ssl-protocols`, `nginx.org/ssl-ciphers` and `nginx.org/ssl-prefer-server-ciphers` are supported. See [ngx_http_ssl_module](https://nginx.org/en/docs/http/ngx_http_ssl_module.html) for more information.
+    - `allowedRoutes`: Supported.
+- `status`
+  - `conditions`: Supported (Condition/Status/Reason):
+    - `Accepted/True/Accepted`
+    - `Accepted/True/ListenersNotValid`
+    - `Accepted/False/NotAllowed`
+    - `Accepted/False/ParentNotAllowed`
+    - `Accepted/False/ListenersNotValid`
+    - `Programmed/True/Programmed`
+    - `Programmed/False/NotAllowed`
+    - `Programmed/False/ParentNotAllowed`
+    - `Programmed/False/ListenersNotValid`
+  - `listeners`
+    - `name`: Supported.
+    - `supportedKinds`: Supported.
+    - `attachedRoutes`: Supported.
+    - `conditions`: Supported (Condition/Status/Reason):
+      - `Accepted/True/Accepted`
+      - `Accepted/False/UnsupportedProtocol`
+      - `Accepted/False/InvalidCertificateRef`
+      - `Accepted/False/ProtocolConflict`
+      - `Accpeted/False/HostnameConflict`
+      - `Accepted/False/UnsupportedValue`
+      - `Accepted/False/RefNotPermitted`
+      - `Programmed/True/Programmed`
+      - `Programmed/False/Invalid`
+      - `ResolvedRefs/True/ResolvedRefs`
+      - `ResolvedRefs/False/InvalidCertificateRef`
+      - `ResolvedRefs/False/InvalidRouteKinds`
+      - `ResolvedRefs/False/RefNotPermitted`
+      - `Conflicted/True/ProtocolConflict`
+      - `Conflicted/True/HostnameConflict`
+      - `Conflicted/False/NoConflicts`
+      - `OverlappingTLSConfig/True/OverlappingHostnames`
+
 ### Custom Policies
 
 {{< table >}}