Need Clarification: In GRPCRoute, does the type of method match count for priority?

[randmonkey]

In the specification of precedence of GRPCRoute rules here https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRouteRule:

Precedence MUST be given to the rule with the largest number of:

  - Characters in a matching non-wildcard hostname.
  - Characters in a matching hostname.
  - Characters in a matching service.
  - Characters in a matching method.
  - Header matches.

The Type of method match is not mentioned here. I want to get a explanation about the priority of Type field in method match:

• Does it count in precedence?
• Should Exact method match take precedence over method match with other types?
  For example, if two rules like this

matches:
- method:
    type: Exact
    service: v1
    method: foo
backendrefs:
- name: service1
  port: 80

and

matches:
- method:
    type: RegularExpression
    service: v1
    method: [a-z]+
backendrefs:
- name: service2
  port: 80

Which service will A GRPC request to /v1/foo go? According to the specification where there is no place for priority of Type of the match, the latter one will be matched and the request will go to service2. This seems weird when the non-exact match took the precedence over the exact match. So I need clarification here on the priority of type field in method match here. What is the intention on the priority of the fields in method match here?

[robscott]

/cc @gnossen

[shaneutt]

Seems like more information and discussion are needed here:

/triage needs-information

But given that this is about GRPCRoute it doesn't appear this is something that we need to sort out before GA.

[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.