fix(acl): allow Honey to reach MCP proxies (TIN-2940) - #18
Merged
Conversation
|
Jesssullivan
force-pushed
the
fix/tin-2940-honey-mcp-acl
branch
from
July 16, 2026 10:27
9f0ec82 to
bce4080
Compare
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.
Why
The pooled MCP canary runs on Honey. Tailscale proxy logs show Honey-to-MCP TCP/8080 dropped with
no rules matched. The existingtag:k8sidentity covers the broader Kubernetes fleet and is too wide for this exception.Change
tag:mcp-proxyidentity owned bytag:k8s-operatortinyland-honeyhost totag:mcp-proxyontcp:8080tag:k8sruleDeployment ordering
tag:mcp-proxy.tag:k8sand addtag:mcp-proxy.No Service recreation, workload deployment, or local ACL push is part of this PR.
Evidence
tailscale pingHoney ->mcp-fetch-2succeedsLinear: TIN-2940