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
|[GatewayClass](#gatewayclass)|Supported | Not supported | Not Supported | v1beta1 |
10
+
|[Gateway](#gateway)|Supported | Not supported | Not Supported | v1beta1 |
11
+
|[HTTPRoute](#httproute)|Supported | Partially supported | Not Supported | v1beta1 |
12
+
|[ReferenceGrant](#referencegrant)|Supported | N/A | Not Supported | v1beta1 |
13
+
|[Custom policies](#custom-policies)| Not supported | N/A | Not Supported | N/A |
14
+
|[TLSRoute](#tlsroute)| Not supported | Not supported | Not Supported | N/A |
15
+
|[TCPRoute](#tcproute)| Not supported | Not supported | Not Supported | N/A |
16
+
|[UDPRoute](#udproute)| Not supported | Not supported | Not Supported | N/A |
17
17
18
18
## Terminology
19
19
20
-
-*Support Level*. See the Gateway API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/#2-support-levels).
20
+
Gateway API features has three [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/#2-support-levels):
21
+
Core, Extended and Implementation-specific. We use the following terms to describe the support status for each level and
22
+
resource field:
23
+
21
24
-*Supported*. The resource or field is fully supported.
22
25
-*Partially supported*. The resource or field is supported partially or with limitations. It will become fully
23
26
supported in future releases.
24
27
-*Not supported*. The resource or field is not yet supported. It will become partially or fully supported in future
25
28
releases.
26
29
27
-
Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway
28
-
API. We will document these decisions on a case by case basis.
30
+
> Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. We will document these decisions on a case by case basis.
31
+
32
+
> NGINX Kubernetes Gateway doesn't support any features from the experimental release channel.
29
33
30
34
## Resources
31
35
@@ -36,10 +40,13 @@ the [Gateway API documentation](https://gateway-api.sigs.k8s.io/references/spec/
36
40
37
41
### GatewayClass
38
42
39
-
> Support Level: Core.
43
+
> Support Levels:
44
+
> - Core: Supported.
45
+
> - Extended: Not supported.
46
+
> - Implementation-specific: Not supported.
40
47
41
-
NGINX Kubernetes Gateway supports only a single GatewayClass resource configured via `--gatewayclass` flag
42
-
of the [static-mode](./cli-help.md#static-mode) command.
48
+
NGINX Kubernetes Gateway supports only a single GatewayClass resource configured via `--gatewayclass` flag of
49
+
the [static-mode](./cli-help.md#static-mode) command.
43
50
44
51
Fields:
45
52
@@ -56,11 +63,13 @@ Fields:
56
63
57
64
### Gateway
58
65
59
-
> Support Level: Core.
66
+
> Support Levels:
67
+
> - Core: Supported.
68
+
> - Extended: Not supported.
69
+
> - Implementation-specific: Not supported.
60
70
61
71
NGINX Kubernetes Gateway supports only a single Gateway resource. The Gateway resource must reference NGINX Kubernetes
62
-
Gateway's corresponding GatewayClass.
63
-
See [static-mode](./cli-help.md#static-mode) command for more info.
72
+
Gateway's corresponding GatewayClass. See [static-mode](./cli-help.md#static-mode) command for more info.
64
73
65
74
Fields:
66
75
@@ -116,7 +125,10 @@ Fields:
116
125
117
126
### HTTPRoute
118
127
119
-
> Support Level: Core.
128
+
> Support Levels:
129
+
> - Core: Supported.
130
+
> - Extended: Partially supported.
131
+
> - Implementation-specific: Not supported.
120
132
121
133
Fields:
122
134
@@ -147,11 +159,11 @@ Fields:
147
159
* `Accepted/False/NoMatchingListenerHostname`
148
160
* `Accepted/False/NoMatchingParent`
149
161
* `Accepted/False/NotAllowedByListeners`
150
-
* `Accepted/False/UnsupportedValue` - custom reason for when the HTTPRoute includes an invalid or unsupported
151
-
value.
162
+
* `Accepted/False/UnsupportedValue` - custom reason for when the HTTPRoute includes an invalid or
163
+
unsupported value.
152
164
* `Accepted/False/InvalidListener` - custom reason for when the HTTPRoute references an invalid listener.
153
-
* `Accepted/False/GatewayNotProgrammed` - custom reason for when the Gateway is not Programmed. HTTPRoute may
154
-
be valid and configured, but will maintain this status as long as the Gateway is not Programmed.
165
+
* `Accepted/False/GatewayNotProgrammed` - custom reason for when the Gateway is not Programmed. HTTPRoute
166
+
may be valid and configured, but will maintain this status as long as the Gateway is not Programmed.
0 commit comments