Merged
Conversation
Signed-off-by: Evaline Ju <69598118+evaline-ju@users.noreply.github.com>
mvle
approved these changes
Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
As detailed in this comment, v0.5.1 changes to MCP gateway for the operator-based deployment changed the namespace for MCP gateway filter deployment. Because the plugin adapter ext-proc filter here was still in the root namespace, the filter ordering unintentionally changed. To keep the default ordering to post MCP gateway router, a priority is introduced here, but users are free to change the namespace deployed for this filter as well to match the MCP gateway filter namespace if the MCP gateway is available.
Related issue(s)
Fixes #85