fix: add default resource limits to MCPRemoteProxy #3132
+357
−282
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.
Fixes #3131
This PR adds default resource limits to
MCPRemoteProxyto prevent containers from consuming unlimited resources, aligning with the pattern established inVirtualMCPServer(#2873).Changes
BuildDefaultProxyRunnerResourceRequirementsandMergeResourceRequirementstocontrollerutil.mcpremoteproxy_deployment.goto apply default resources (50m/200m CPU, 64Mi/256Mi Memory) when creating deployments.mcpremoteproxy_controller.goto correctly detect updates by comparing against merged resource requirements.mcpremoteproxy_deployment_test.goto verify: