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
networking: support pathTemplate URI matching in VirtualService
Add support for the pathTemplate match type in VirtualService
HTTPMatchRequest.uri, using Envoy's URI template path matching
extension (UriTemplateMatchConfig). This is consistent with the
existing path template support in AuthorizationPolicy.
- Route conversion: StringMatch_PathTemplate maps to
RouteMatch_PathMatchPolicy with the uri_template_matcher extension,
reusing the existing PathTemplateMatcher() from the authz matcher
package for sanitization ({*}->*, {**}->**)
- Validation: pathTemplate is validated via CheckValidPathTemplate()
(same as AuthorizationPolicy) and is restricted to uri matches only
- Delegate conflict detection: pathTemplate is treated as incompatible
with delegate VirtualService composition
- Gateway API: getURIRank/getURILength updated to handle pathTemplate
Depends on istio/api#3675Fixesistio#59533
Signed-off-by: Antonio <antoniomorales9711@gmail.com>
**Added** support for `pathTemplate` URI matching in VirtualService `HTTPMatchRequest`, using `{*}` (matches one path segment) and `{**}` (matches one or more path segments) operators. This is backed by Envoy's URI template path matching extension and is consistent with the existing `pathTemplate` support in `AuthorizationPolicy`. See https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/path/match/uri_template/v3/uri_template_match.proto
0 commit comments