fix(mcp): move backend endpoints to first-level mcp-<name> hostnames - #28
Merged
Conversation
Cloudflare Universal SSL covers only *.makeitwork.cloud, so <name>.mcp.makeitwork.cloud cannot present a certificate and the edge refuses the TLS handshake. Rename to mcp-<name>.makeitwork.cloud and replace the wildcard Access app with one application per backend FQDN.
OpenTofu Plan |
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.
What
Cloudflare Universal SSL covers only
*.makeitwork.cloud, so<name>.mcp.makeitwork.cloudcannot present a certificate — the edge refuses the TLS handshake (verified: ssl alert 40 vs working 2nd-level name).cf-tunnels.tf: backend CNAMEs renamed<name>.mcp→mcp-<name>(locals restructured:mcp_backends+ concat)cf-access-mcp.tf: wildcard Access app replaced by onemcp_gateway_backendapplication per backend FQDN (for_each), same service-token + admins policiesOrdering
The kustomize-cluster TunnelBinding subjects for the old names were withdrawn first (commit 351efd8, per AGENTS.md remove-before-rename). After this applies, subjects return with the new FQDNs, then client configs land.