-
Notifications
You must be signed in to change notification settings - Fork 131
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Broker silently drops upstreams that negotiate an older 2025 revision or run stateless (no Mcp-Session-Id)
triage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1451 In Kuadrant/mcp-gateway;e2e + docs: 2026-only gateways scale horizontally without Redis
priority/normalCan be worked on after critical and high priority items are accounted forCan be worked on after critical and high priority items are accounted fortriage/acceptedHas been assessed, and accepted for workHas been assessed, and accepted for workStatus: Open.MCPServerRegistration never re-reads a corrected credentialRef Secret while its MCPGatewayExtension is NotReady
area/user-experienceImprovements that are relevant to end-user experienceImprovements that are relevant to end-user experiencepriority/highShould be worked on first, prior to any normal or low priority itemsShould be worked on first, prior to any normal or low priority itemspriority/normalCan be worked on after critical and high priority items are accounted forCan be worked on after critical and high priority items are accounted forsize/MMedium: moderate scope, straightforward reviewMedium: moderate scope, straightforward reviewtriage/acceptedHas been assessed, and accepted for workHas been assessed, and accepted for workStatus: Open.refactor: centralise config secret writes and remove --max-request-body-size flag
area/maintenanceMaintenance and development of existing capabilitiesMaintenance and development of existing capabilitiestriage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1444 In Kuadrant/mcp-gateway;refactor: remove --max-request-body-size CLI flag in favour of spec.maxBodyBytes
area/maintenanceMaintenance and development of existing capabilitiesMaintenance and development of existing capabilitiestriage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1443 In Kuadrant/mcp-gateway;refactor: deduplicate TLS cert pool construction across 4 call sites
area/maintenanceMaintenance and development of existing capabilitiesMaintenance and development of existing capabilitiestriage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1442 In Kuadrant/mcp-gateway;feat(guardrails): add response-side tools/call for 2025 SSE/Event-Stream
triage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1440 In Kuadrant/mcp-gateway;feat(guardrails): add response-side tools/call for 2026 JSON response path
triage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1439 In Kuadrant/mcp-gateway;Broker silently excludes upstreams negotiating a non-pinned 2025-series protocol version (e.g. 2025-03-26) from all served sets
triage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1436 In Kuadrant/mcp-gateway;mcp-controller unconditionally writes HTTPRoute spec.rules[].name, breaking on OpenShift (Gateway API v1.3.0, no graceful fallback)
triage/needs-triageIssues that need review and decisions about their milestones and priorityIssues that need review and decisions about their milestones and priorityStatus: Open.#1431 In Kuadrant/mcp-gateway;Broker sends session-less liveness ping to upstream MCP servers; rejected by strict streamable-HTTP servers (mcp-searxng 2.0.0)
area/maintenanceMaintenance and development of existing capabilitiesMaintenance and development of existing capabilitiespriority/highShould be worked on first, prior to any normal or low priority itemsShould be worked on first, prior to any normal or low priority itemssize/MMedium: moderate scope, straightforward reviewMedium: moderate scope, straightforward reviewtriage/acceptedHas been assessed, and accepted for workHas been assessed, and accepted for workStatus: Open.Add protocol.version span attribute consistently across router and broker
area/maintenanceMaintenance and development of existing capabilitiesMaintenance and development of existing capabilitiespriority/lowCan be worked on last, after all higher priority issues are accounted forCan be worked on last, after all higher priority issues are accounted forsize/SSmall: isolated change, minimal reviewSmall: isolated change, minimal reviewtriage/acceptedHas been assessed, and accepted for workHas been assessed, and accepted for workStatus: Open.