Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple RouteMatches #520

Open
solmonk opened this issue Nov 17, 2023 · 0 comments
Open

Support multiple RouteMatches #520

solmonk opened this issue Nov 17, 2023 · 0 comments

Comments

@solmonk
Copy link
Contributor

solmonk commented Nov 17, 2023

example config brought from #75:

---
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: HTTPRoute
metadata:
  name: frontend
  namespace: default
spec:
  parentRefs:
  - name: eks-store-network
    sectionName: http 
    namespace: default
  rules:
  - backendRefs:  
    - name: frontend-svc
      kind: Service
      port: 3000
      namespace: default
    matches:
    - path:
        type: PathPrefix
        value: /summary    
    - path:
        type: PathPrefix
        value: /popular

By GWAPI spec, the rule should match on "either of" the conditions. VPC Lattice only support AND matches at the moment so the controller is rejecting such rules by returning LATTICE_NO_SUPPORT_FOR_MULTIPLE_MATCHES.

This can be internally implemented by creating a new rule for each of the match. The caveat is we will reach VPC Lattice rule limit quicker (5 rules per listener by default)

@solmonk solmonk changed the title Support multiple RouteMatch Support multiple RouteMatches Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant