Add Tailscale as a sidecar if enabled #162
Open
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.
Description of the change
Uptime Kuma natively supports pinging with the Tailscale VPN on the non-Dockerized version. I find it regrettable that we can't bridge with a Tailscale container in sidecar mode.
Therefore, I have added support, which can be enabled or not, with or without root, from the official Tailscale documentation in the chart.
The default values do not change the behavior of the chart.
Benefits
With a Tailscale device in sidecar mode, it is possible to access all the devices on the network directly via their IP, enabling all the monitoring supports that Uptime Kuma offers. Depending on the defined ACLs, it is also possible to access Uptime Kuma from the Tailscale network.
Possible drawbacks
To have direct access to the Tailscale network from Uptime Kuma without using the proxy option, the Tailscale in sidecar mode must run as root, which reduces security. See the documentation kubernetes#userspace-sidecar.
Root mode can be disabled via values.
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver.