feat: Add dedicated MCP server container in the Feast operator Deployment - #6654
Draft
patelchaitany wants to merge 1 commit into
Draft
feat: Add dedicated MCP server container in the Feast operator Deployment#6654patelchaitany wants to merge 1 commit into
patelchaitany wants to merge 1 commit into
Conversation
…ment The MCP server currently runs inside the same container as the online feature server, sharing the same port, process, and resources. This change adds a dedicated MCP container in the existing Feast pod with its own port, resource limits, and Kubernetes Service, following the same sidecar pattern as the registry, offline, and UI containers. Closes feast-dev#6653 Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com>
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
1 participant
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
Motivation
The MCP server currently runs inside the same container as the online feature server, sharing the same port, process, and resources. No way to isolate MCP traffic or allocate dedicated resources.
Closes #6653