Feature Overview (aka. Goal Summary)  

Captured groups in the rewrite-target annotation

Goals (aka. expected user outcomes)

Normal rewrite-target works as per given as an example in the openshift documentation. But here requirement is to implement Captured groups in the annotation which is working in Kubernetes with nginx ingress controller as given below in the link
https://kubernetes.github.io/ingress-nginx/examples/rewrite/

Captured groups are saved in numbered placeholders, chronologically, in the form $1, $2 ... $n. These placeholders can be used as parameters in the rewrite-target annotation.

We like to know if this feature is available in HA proxy ingress controller in OCP.

Example: path : www.example.com/somethng/new1/new2/ should be rewrited with path as /new1 or /new2 based on what we pass in the annotation.

Currently Captured groups in the annotation will not work and OpenShift router replaces spec.path with the target specified in the annotation.

https://github.com/openshift/router/blob/0cf6d57113993fe1356ea9b343e547c918ea8da0/images/router/haproxy/conf/haproxy-config.template#L591-L59

Requirements (aka. Acceptance Criteria):

• Need to add a field into route API. 
• https://github.com/openshift/router/blob/6144b9abe85ee434e586eba2f21b6b309357ee78/images/router/haproxy/conf/haproxy-config.template#L591-L598
• http://cbonte.github.io/haproxy-dconv/2.6/configuration.html#4.2-http-request%20replace-path

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.