[Deferred] Rate limiting for MCPRemoteProxy
Open
Nobody has claimed this yet.
api
enhancement
go
kubernetes
operator
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
User Story
As a cluster admin,
I want rate limiting on MCPRemoteProxy,
so that proxied remote MCP traffic is also protected.
Context
Deferred — not part of the initial implementation. Created for visibility.
MCPRemoteProxy shares the same MiddlewareFactory registry as MCPServer, so integration should be straightforward. See THV-0057.
Acceptance Criteria
-
rateLimitingon MCPRemoteProxy spec - Same middleware and config as MCPServer
Dependencies
- STORY-001, STORY-002 (core rate limit infrastructure)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the MCPRemoteProxy spec and the shared MiddlewareFactory registry, then read RFC THV-0057 and the STORY-001/STORY-002 rate-limit infrastructure. Done means MCPRemoteProxy accepts rateLimiting and uses the same middleware and configuration as MCPServer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100