Method based routing

[zoglesby]

I did a quick search and did not see a ticket for this, if I missed it I am sorry.

What would you like to be added:
Method based routing would be a nice addition. This is something that we are currently looking to implement in another part of our stack, but having it in a gateway-api would make things easier for us.

An example of this can be found in Ambassador

---
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: get
spec:
  prefix: /backend/get_only/
  method: GET
  service: quote

https://www.getambassador.io/docs/edge-stack/latest/topics/using/method/#method-based-routing

Why is this needed:
There are many use cases for this, but the my primary need for this is to split read (GET) and write (PUT) traffic to different endpoints.

[robscott]

Thanks for filing this issue! I think we've discussed this in some community meetings and simply failed to create a tracking issue for this feature.

[hbagdi]

What should be the conformance for this?
I'm thinking extended.
Most reverse proxies support it but most cloud LBs don't.

Once we settle on this, it should be possible to add this to the API fairly easily.

[robscott]

I think this is an extended feature since not every implementation will be able to support it, but agree it should be pretty straightforward to add. I'm actually a little tempted to try to get this into v0.3.0 but that's coming up pretty quickly.

[hbagdi]

@zoglesby If you can send a PR for this feature in the next couple days, we might be able to include this feature in our upcoming release. Even if we can't get it in the release, a PR would be warmly welcome!

[bowei]

+1 to extended, agree with all comments above.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[jpeach]

/remove-lifecycle stale
/lifecycle frozen

[hbagdi]

/assign @secustor

[k8s-ci-robot]

@hbagdi: GitHub didn't allow me to assign the following users: secustor.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @secustor

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.