Skip to content

feat: Add dedicated MCP server container in the Feast operator Deployment #6653

Description

@patelchaitany

Is your feature request related to a problem? Please describe.

The MCP server 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.

Describe the solution you'd like

Add a dedicated MCP container in the existing Feast pod with its own port, resource limits, and Kubernetes Service. Same sidecar pattern as the registry, offline, and UI containers.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions