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
Until now, users were only able to use hostnames without wildcards, limiting their options.
We now support wildcard hostnames for HTTPRoutes and Gateway listeners.
*`parentRefs` - partially supported. Port not supported.
104
-
*`hostnames` - partially supported. Wildcard binding is not supported: a hostname like `example.com` will not bind to a listener with the hostname `*.example.com`. However, `example.com` will bind to a listener with the empty hostname.
104
+
*`hostnames` - supported.
105
105
*`rules`
106
106
*`matches`
107
107
*`path` - partially supported. Only `PathPrefix` and `Exact` types.
0 commit comments