Skip to content

fix(grpc-route-match): allow undefined rpc match in MatchRoute defini… - #4606

Open
anthoturc wants to merge 1 commit into
mainfrom
anthoturc/grpcroute-rpc-fix
Open

fix(grpc-route-match): allow undefined rpc match in MatchRoute defini…#4606
anthoturc wants to merge 1 commit into
mainfrom
anthoturc/grpcroute-rpc-fix

Conversation

@anthoturc

Copy link
Copy Markdown
Contributor

…tion

fixes linkerd/linkerd2#14047

@cratelyn

Copy link
Copy Markdown
Member

i see there are some open questions in #14047, here: linkerd/linkerd2#14047 (comment). have we confirmed for sure that this addresses the reported issue? it isn't completely clear to me right now if this is ready to be reviewed.

@cratelyn

Copy link
Copy Markdown
Member

also, noting that we'll need to add sign-off information to the commits in this branch.

@cratelyn cratelyn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments above...

@anthoturc

Copy link
Copy Markdown
Contributor Author

i see there are some open questions in #14047, here: linkerd/linkerd2#14047 (comment). have we confirmed for sure that this addresses the reported issue? it isn't completely clear to me right now if this is ready to be reviewed.

Ah yes, this is a question for the person who set published an image for the repro. I wasn't sure if there was a typo in the print statements of the client application.

By any chance is there a typo in the print statements within the image? The logs in service-a didn't look quite right.

My end-to-end test included TAPping the client/servers and suggested that the fix does address the underlying issue.

I'll DM you to discuss this a little further.

Comment thread linkerd/http/route/src/grpc/match.rs Outdated
@anthoturc
anthoturc force-pushed the anthoturc/grpcroute-rpc-fix branch from 11325b6 to eb7e59a Compare August 27, 2026 02:31
@anthoturc

Copy link
Copy Markdown
Contributor Author

also @cratelyn, i did run the linkerd2 integration tests with the proxy image built from this commit and the same tests pass against main and this branch.

there was one failing test across main and my branch that failed, but it looked related to my setup as opposed to some business logic:

install_test.go:687: Error retrieving resource requirements for linkerd-destination: container linkerd-proxy not found in deployment linkerd-destination in namespace linkerd
  --- FAIL: TestComponentProxyResources (0.00s)
  FAIL
  FAIL    command-line-arguments    131.903s
  FAIL
  Error: uninstall: Release not loaded: multicluster-test: release: not found
  Error from server (NotFound): namespaces "linkerd-multicluster" not found
  release "helm-test-l5d-viz" uninstalled
  namespace "linkerd-viz" deleted
  release "helm-test-control-plane" uninstalled
  release "helm-test-crds" uninstalled
  namespace "linkerd" deleted

everything else passed so i think we should be okay with merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GRPCRoute with header-based match results in invalid client policy error on linkerd sidecar and result in connection errors and failures

2 participants