Open rokkiter opened 10 months ago
looks like a dup of https://github.com/kubernetes-sigs/gateway-api/issues/2177, @rokkiter you would also need to update the GEP before adding in the API changes
Yes, our purpose is similar, I am going to create a new gep to drive this
Because doing regex path rewrites involves doing a regex path match, followed by using captured info in a rewrite filter, I think that #2177 covers just adding the match criteria as well. See my comment on that for more thoughts on what the resulting GEP will need to address.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
What would you like to be added:
In gep-726,. it is mentioned that Regula......dsarExpression will be added to HttpRouter as a Future Extension. Hope to promote the implementation of RegularExpression.
Why this is needed: I think RegularExpression is a function with a very wide range of usage scenarios. If route matching cannot be supported natively, we need to implement it in a very complicated way. For example, in istio, the redirect function cannot support regex matching. I can only use envoyfilter to achieve. Because the Gateway API is a standard, if the Gateway API does not support RegularExpression, the istio community's support for regex matching will also be affected. I believe other communities have similar problems.
Istio issue: https://github.com/istio/istio/issues/47500 for support RegularExpression.