Alternative to get same capability of extensionRef from route match block after discontinuing support for it

[Amila-Rukshan]

What would you like to be added:
With the following GEP, the extension points within Route match block are going to be removed.
https://gateway-api.sigs.k8s.io/geps/gep-820/

If I had the some policy defined and targeted at HTTPRoute resource then it will apply for all the route rules. but previously it was possible to apply for a single rule (that granularity is lost after dropping the extensionRef support from filters).

I would like to suggest a way as below. If we modify the target-ref-api to support custom properties listed under another property with the value of kind property.

kind: SomePolicy
metadata:
  name: ...
spec:
  default:
    type: <type>
    <type>:
      ...              # policy specific properties          
      ...
targetRef:             
    kind: HTTPRoute  
    name: resource-name
    hTTPRoute:
        ruleNames: 
           - my-rule-name-1

apiVersion: gateway.networking.k8s.io/v1alpha2
kind: HTTPRoute
metadata:
  name: httpbin
spec:
  parentRefs:
    - name: eg
  hostnames:
    - "www.example.com"
  rules:
    - name: my-rule-name-1
      backendRefs:
        - group: ""
          kind: Service
          name: httpbin-1
          port: 80
          weight: 1
       matches:
        - path:
            type: PathPrefix
            value: /
    - name: my-rule-name-2
       backendRefs:
        - group: ""
          kind: Service
          name: httpbin-2
          port: 80
          weight: 1
       matches:
        - path:
            type: PathPrefix
            value: /
  

Now the policy is applied to the rule of the HTTPRoute and not all the rules.

Why this is needed:

This will help not to split related http routes (going to the same backend and same filters are applied) into a set of HTTPRoute resources by targeting the policy to the HTTPRouteRule.

[johnlanni]

+1

related discussion: #996

[robscott]

Hey @Amila-Rukshan is there a specific kind of matching you'd like to enable? Wherever possible, we're trying to define common APIs for matching, as long as the concept is broadly implementable.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.