Skip to content

fix(helm): add MCP HTTPRoute configuration#42219

Open
dmunozv04 wants to merge 1 commit into
apache:masterfrom
dmunozv04:helm-chart-mcp-httproute
Open

fix(helm): add MCP HTTPRoute configuration#42219
dmunozv04 wants to merge 1 commit into
apache:masterfrom
dmunozv04:helm-chart-mcp-httproute

Conversation

@dmunozv04

Copy link
Copy Markdown
Contributor

SUMMARY

#41073 introduced HTTPRoute support for the helm chart, but it didn't include a rule for the MCP deployment.

PS: I'll try to make this one be my last PR in regards to the helm chart.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A

TESTING INSTRUCTIONS

When #42206 is merged, helm-unittest will run on CI.

Alternatively, it can be tested by deploying the chart with the following values:

supersetMcp:
  enabled: true
  httproute:
    enabled: true

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@bito-code-review bito-code-review Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review Agent Run #fb94a9

Actionable Suggestions - 1
  • helm/superset/tests/httproute_test.yaml - 1
Additional Suggestions - 1
  • helm/superset/tests/httproute_test.yaml - 1
    • Missing combined feature test · Line 65-65
      No test exists for the combined scenario where both websockets and MCP are simultaneously enabled. Without this coverage, the rule ordering at lines 71-94 (websocket before MCP) is never validated in combination.
Review Details
  • Files reviewed - 4 · Commit Range: c552f42..c552f42
    • helm/superset/Chart.yaml
    • helm/superset/templates/httproute.yaml
    • helm/superset/tests/httproute_test.yaml
    • helm/superset/values.yaml
  • Files skipped - 1
    • helm/superset/README.md - Reason: Filter setting
  • Tools
    • Whispers (Secret Scanner) - ✔︎ Successful
    • Detect-secrets (Secret Scanner) - ✔︎ Successful

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

  • /review - Manually triggers a full AI review.

  • /pause - Pauses automatic reviews on this pull request.

  • /resume - Resumes automatic reviews.

  • /resolve - Marks all Bito-posted review comments as resolved.

  • /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Superset You can customize the agent settings here or contact your Bito workspace admin at evan@preset.io.

Documentation & Help

AI Code Review powered by Bito Logo

Comment on lines +65 to +79
- it: routes the MCP path when MCP HTTPRoute is enabled
set:
httproute.enabled: true
supersetMcp.enabled: true
supersetMcp.httproute.enabled: true
asserts:
- equal:
path: spec.rules[1].backendRefs[0].name
value: RELEASE-NAME-superset-mcp
- equal:
path: spec.rules[1].backendRefs[0].port
value: 5008
- equal:
path: spec.rules[1].matches[0].path.value
value: /mcp

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing rule count assertion

The MCP test lacks a rule count assertion. Without it, the test passes even if unexpected extra rules exist. This test should mirror the pattern used in the WebSocket test (lines 43-45) which explicitly asserts count: 2.

Code Review Run #fb94a9


Should Bito avoid suggestions like this for future reviews? (Manage Rules)

  • Yes, avoid them

@rusackas rusackas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dmunozv04, this mirrors the websocket rule pattern nicely and the port/path all check out. Bito's flagging a missing rule-count assertion on the new MCP test in httproute_test.yaml (around line 65), might be worth adding a lengthEqual check there like the websocket test above it has. LGTM otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants