FR: Allow custom domains for Tailscale Funnel
### What are you trying to do? I would like to expose a service to the public Internet using a custom domain name without requiring CNAME records, ideally via the Kubernetes operator. ### How should we solve this? I haven't thought deeply about this, but in the context of the Tailscale operator, I think this could be implemented by extending `tailscale serve` to function as a full reverse proxy that allows multiple routes with distinct hostnames and certs OR by updating the operator to use an existing reverse proxy side car (e.g., nginx) and configuring it based on the ingress specification. ### What is the impact of not solving this? Workarounds require running a node with a public IP address to bridge to the tailnet and leaving users to manage their own certificates, which pretty much obviates the benefits of funnel as far as I can tell. ### Anything else? _No response_
Posted by weberc2 on Mar 29, 2024, 7:32 PM
Tags
Related issues
- [UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
- Server requests and latency increased after upgrading from Next.js 15 to 16
- Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
- Can't download videos from YouTube on cobalt.tools
- `google_service_networking_connection` produce an error when trying to destroy the resource
- WebGPU-based renderer for the editor
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Network)
[UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
Server requests and latency increased after upgrading from Next.js 15 to 16
Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
Can't download videos from YouTube on cobalt.tools
`google_service_networking_connection` produce an error when trying to destroy the resource
WebGPU-based renderer for the editor
Zed downloads NodeJS binary and npm packages from Internet without user’s consent
FR: Allow custom domains for Tailscale Funnel
FR: Allow custom domains for Tailscale Funnel
### What are you trying to do? I would like to expose a service to the public Internet using a custom domain name without requiring CNAME records, ideally via the Kubernetes operator. ### How should we solve this? I haven't thought deeply about this, but in the context of the Tailscale operator, I think this could be implemented by extending `tailscale serve` to function as a full reverse proxy that allows multiple routes with distinct hostnames and certs OR by updating the operator to use an existing reverse proxy side car (e.g., nginx) and configuring it based on the ingress specification. ### What is the impact of not solving this? Workarounds require running a node with a public IP address to bridge to the tailnet and leaving users to manage their own certificates, which pretty much obviates the benefits of funnel as far as I can tell. ### Anything else? _No response_
Comments (0)
No comments yet. Start the discussion.