Capturing groups when using Kong Ingress Controller

[ozrlz]

Has anyone been able to define Capturing groups [1] as paths on a Kubernetes Ingress Resource when using the kong ingress controller?
According to [2], kong api gateway and kubernetes support different regex, I tried using /base/(?<var_name>[a-z]+), but this is not a valid regex for the kubernetes ingress resource.

What I try to achieve is to rewrite [3] all paths that match the /base/ endpoint and rewrite it to /different_base/v1 endpoint as pointed on this Github Issue [4].

[1] - https://docs.konghq.com/0.14.x/proxy/#capturing-groups
[2] - Kong ingress controller and path based routing - #6 by hbagdi
[3] - GitHub - stone-payments/kong-plugin-url-rewrite: Kong API Gateway plugin for url-rewrite purposes
[4] - Rewrite dynamic part of URL · Issue #21 · stone-payments/kong-plugin-url-rewrite · GitHub

[hbagdi]

Please have a look at the following post:

Kong ingress controller and path based routing

It turns out that Ingress Spec supports the POSIX regular expression (as defined by IEEE Std 1003.1) and not PCRE, which is used by Kong. This means that you can use only a subset of regular expressions that are valid POSIX regexes. Since, it’s an ID that you are trying express, I imagine it would be possible for you to know which characters can be present in the ID? The following Ingress is satisfied and works properly for me, and you can build up on top of it: apiVersion: extensions/v1beta…

The regex supported by Ingress spec are POSIX based and not PCRE.