Write GEP for specifying path segment match in HTTPRoute of gateway API

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Does this enhancement require public documentation?

• I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

Currently HTTPRoute does not have a path match type of segment matching, neither does it have an "implementation specific" match. Also it does not allow custom path match type of in its CRD definition. With the current definition of HTTPRoute in gateway APIs, we have to specify path segment match as RegularExpression type of path match and use certain annotation and prefix of path. This does not satisfy the definition of RegularExpression match.
To specify path segment match in a more canonical way, we need to make upstream support a dedicated path match type for it.

Proposed Solution

• Write a GEP for proposing a path match type of path segment match
• When it is accepted, implement the definition and conformance tests for path segment match

Additional information

No response

Acceptance Criteria

• The GEP of adding path match type for path segment match is accepted by upstream of gateway API
• Implement the specification of the API and conformance tests
• Implement path segment match in KIC based on the API definition and pass the tests
• Update the docs to describe the usage and specification of path segment match