fix(opencode): route in-cluster clients directly to MCP backends - #98
Merged
Merged
Conversation
Chart CI passedRepository hygiene and Helm validation passed. View the workflow run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Routes OpenCode directly to its in-cluster ToolHive MCP backend proxy Services and reserves
vmcp-gatewayfor external consumers. Updates root and packaged routing instructions, chart documentation, and affected S3, SlideSpeak, and Twilio documentation skills.Fixes #
N/A — owner-approved routing correction.
Type of change
Validation
opencode-serverpackaging. These validate chart content, not runtime MCP reachability.files/inputs through Helm; no generated source was edited.Impact and rollout
Producer:
opencode-serverchart0.1.78; consumer: OpenCode sessions selected through the downstreamkustomize-clusterApplication pin.Before the generated GitOps pin is selected, all 14 direct ToolHive proxy Services must be reconciled and healthy. After the pin merges and Argo CD reconciles, verify a fresh OpenCode session discovers the direct tool names and performs bounded read-only representative calls. The external
vmcp-gatewayaggregate remains unchanged.After a confirmed merge, charts publishes the immutable OCI package and automation opens or updates the separate
kustomize-clusterpin PR. That desired-state PR, its checks, reconciliation, health, and functional verification remain separate gates.Rollback is a manual GitOps pin selection to an earlier immutable chart version; before selecting an aggregate-era version, verify
vmcp-gatewayand required members remain available.Safety and secrets
makeitwork_prefix; affected packaged guidance is updated and post-rollout discovery is required.AI-assisted change; reviewer scrutiny requested.