Tailscale: Add support for serve/funnel and certs

[1vivy]

Is your feature request related to a problem?

Tailscale has an embedded proxy and certificate service that allows exposing ports & https to the internet, or other users in a Tailnet (Tailscale network).

Describe the solution you'd like

• Tailscale needs a persistent folder to store it's certificates (I used /var/lib/tailscale/ since it's already persistent)
• Tailscale needs access to TrueNAS and other apps ports to proxy (I used host networking & disabled userspace mode)

My needs are simple, I don't have any apps on TrueNAS nor need to expose any routes in my network. I was able to do this through shell without any change to the image/repo:

• Turn off Userspace
• Turn on Host Network

  $ cd /var/lib/tailscale
  $ tailscale cert xxxx.XXXX-XXXX.ts.net (type 'tailscale cert' to get your domain address)
  $ tailscale serve https / http://127.0.0.1:80
  $ tailscale funnel 443 on (not the best idea to expose TrueNAS GUI to the web, but good if you're proxying something else)

The closest thing to my current solution is probably: https://github.com/lmagyar/homeassistant-addon-tailscale

Describe alternatives you've considered

There is work using Tailscale with Traefik, Tailscale as a Caddy plugin to expose apps as their own node, Tailscale on Kubernetes (as an ingress controller). I.e. https://tailscale.dev/blog/docker-mod-tailscale

Ideally the end product is something that works for apps in the TrueNAS scale/TrueCharts environment. My solution works also.

Additional context

8877 Has been locked down and limited to collaborators only. I would have post my interest on there.

I've read and agree with the following

• [X] I've checked all open and closed issues and my request is not there.
• [X] I've checked all open and closed pull requests and my request is not there.

[PrivatePuffin]

First off: Due to relying heavily on the domain being set in ingress, this is not likely to be added. But the parts that need to be set, can be set already, as you've noticed.

The prefered solution is traefik integration (in due time), as that should(tm) be ingress compatible. But that still requires R&D from our side.

However: As you;ve said https://github.com/truecharts/charts/issues/8877 already exists and is locked for a reason because we don't need more info on it nor +1's.

I'm going to give you a repo timeout for making new tickets to, essentially, +1 this. We've a discord for a reason if you really wanted to communicate some technical notes on an issue that's closed.

[truecharts-admin]

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists