You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: GatewayClass had duplicate info, and was missing its header at the top.
Solution: Move GatewayClass header to where it belongs and remove duplicate info.
| GatewayClass | Supported | Not supported | Not supported | v1 |
52
+
{{< /bootstrap-table >}}
53
+
54
+
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.
55
+
56
+
**Fields**:
57
+
46
58
-`spec`
47
59
-`controllerName` - supported.
48
60
-`parametersRef` - not supported.
@@ -120,30 +132,6 @@ See the [static-mode]({{< relref "/reference/cli-help.md#static-mode">}}) comman
| GatewayClass | Supported | Not supported | Not supported | v1 |
129
-
{{< /bootstrap-table >}}
130
-
131
-
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.
-`Accepted/False/GatewayClassConflict`: Custom status for when GatewayClass references this controller, but a different GatewayClass name is provided to the controller via the command-line argument.
0 commit comments