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
Add support for specifying AllowedRoutes in Listeners. A user can now allow/disallow routes based on namespace. Either all namespaces, same namespace, or label selectors can be used to determine which routes are allowed.
*`certificateRefs` - partially supported. The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls` in the same namespace as the Gateway resource. Only a single reference is supported. You must deploy the Secret before the Gateway resource. Secret rotation (watching for updates) is not supported.
66
66
*`options` - not supported.
67
-
*`allowedRoutes` - not supported.
67
+
*`allowedRoutes` - supported.
68
68
*`addresses` - not supported.
69
69
*`status`
70
70
*`addresses` - Pod IPAddress supported.
@@ -122,6 +122,7 @@ Fields:
122
122
*`Accepted/True/Accepted`
123
123
*`Accepted/False/NoMatchingListenerHostname`
124
124
*`Accepted/False/NoMatchingParent`
125
+
*`Accepted/False/NotAllowedByListeners`
125
126
*`Accepted/False/UnsupportedValue`: Custom reason for when the HTTPRoute includes an invalid or unsupported value.
126
127
*`Accepted/False/InvalidListener`: Custom reason for when the HTTPRoute references an invalid listener.
127
128
*`Accepted/False/GatewayNotProgrammed`: Custom reason for when the Gateway is not Programmed. HTTPRoute may be valid and configured, but will maintain this status as long as the Gateway is not Programmed.
0 commit comments