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

MeshHttpRoute Not Being Applied #10204

Open
stephen-galea-weavr opened this issue May 8, 2024 · 3 comments
Open

MeshHttpRoute Not Being Applied #10204

stephen-galea-weavr opened this issue May 8, 2024 · 3 comments
Assignees
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this

Comments

@stephen-galea-weavr
Copy link

What happened?

I would like to mirror calls between two services using the MeshHttpRoute policy but it is not being applied.

This is my sample config:

kind: MeshHTTPRoute
metadata:
  name: mirror-ehi
  namespace: kuma-system
  labels:
    kuma.io/mesh: default
spec:
  targetRef:
    kind: MeshService
    name: backend-xx-caddy_qa_svc_5555
  to:
    - targetRef:
        kind: MeshService
        name: backend-yy_qa_svc_8281
      rules:
        - matches:
           - headers:
              - type: Exact
                name: mirror-this-request
                value: "true"
          default:
            filters:
              - type: RequestMirror
                requestMirror:
                  percentage: 100
                  backendRef:
                    kind: MeshService
                    name: pn-zzz_qa_svc_8000
            backendRefs:
              - kind: MeshService
                name: backend-yy_qa_svc_8281

I have even tried to apply a traffic split policy but again it seems to be ignored.

apiVersion: kuma.io/v1alpha1
kind: MeshHTTPRoute
metadata:
  name: ehi-route
  namespace: kuma-system
  labels:
    kuma.io/mesh: default
spec:
  targetRef:
    kind: MeshService
    name: backend-xxx-caddy_qa_svc_5555
  to:
    - targetRef:
        kind: MeshService
        name: backend-yyy_qa_svc_8281
      rules:
        - matches:
            - path:
                type: PathPrefix
                value: /ehi
          default:
            backendRefs:
              - kind: MeshService
                name: backend-yyy_qa_svc_8281
                weight: 50
              - kind: MeshService
                name: pn-zzzqa_svc_8000
                weight: 50
@stephen-galea-weavr stephen-galea-weavr added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels May 8, 2024
@stephen-galea-weavr
Copy link
Author

It seems the mirror is now working, however I had to restart the control plane for it to apply correctly.

@jakubdyszkiewicz
Copy link
Contributor

Triage: do you applied this on Global CP with a multizone deployment or did you apply this on Zone CP?

What is the version of Kuma?
Thanks!

@jakubdyszkiewicz jakubdyszkiewicz added triage/needs-information Reviewed and some extra information was asked to the reporter and removed triage/pending This issue will be looked at on the next triage meeting labels May 13, 2024
@stephen-galea-weavr
Copy link
Author

Single Zone CP. I was running 2.7.1 and then updated to 2.7.2 which reset the CP of course and then started working.

@jakubdyszkiewicz jakubdyszkiewicz added triage/needs-reproducing Someone else should try to reproduce this and removed triage/needs-information Reviewed and some extra information was asked to the reporter labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this
Projects
None yet
Development

No branches or pull requests

3 participants