-
Notifications
You must be signed in to change notification settings - Fork 144
removes unused cli flags from proxyrunner #2515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
…ive into removes-flags-proxyrunner
Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2515 +/- ##
==========================================
- Coverage 55.69% 55.66% -0.03%
==========================================
Files 295 295
Lines 28086 28086
==========================================
- Hits 15643 15635 -8
- Misses 11017 11030 +13
+ Partials 1426 1421 -5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jhrozek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the LLM catch about nil,nil is good, but feel free to patch it in a follow-up
It’s been long enough that we can safely remove the unused CLI flags from the proxy runner. An issue was recently raised due to old CLI flags overriding newer configurations. Since the Operator now relies entirely on runconfig files rather than CLI arguments, it’s safe to proceed with their removal.
The only CLI flags currently used by the proxy runner are:
k8s-pod-patch(I have some thoughts on whether this is even necessary for the Kubernetes pod patch. We might be able to handle this via the runconfig as well. I’ll raise that separately.)mcpServerImage := args[0]The Operator also passes the
--foregroundflag, but this is a leftover from when we used the oldtoolhiveapp image. The proxy runner image always runs in the foreground, making this flag redundant for the Operator to pass through.This PR:
foregroundflag from being passed from the Operator to the proxy runnerrunWithFileBasedConfigfunction fromexecution.gointo therun.goto reduce amount of unnecessary filesThere was also an issue reported in #2450 where any CMD args specified in the
MCPServermanifest were not being applied to the MCP server pod. Although they were included in the runconfig ConfigMap undercmd_args, they weren’t set on the pod because they were being overridden by an empty list. This happened because the Operator no longer passes those values. Removing the old flags resolves this issue and cleans up the code.Fixes: #2450
Ref: #2195