Why not use Tailscale on each device?
No need to expose any ports, no need for a bastion, no need for any complicated method of retrieving their public IP address, can use ACLs to restrict their access to other devices on the tailnet (if they’re tech-savvy enough to go looking at the tailnet in the first place).
Essentially, as long as they have internet and Tailscale is running, you’ll be able to connect to their device without exposing anything over the internet.
That is what it means, If the movie in your library is not on one of your lists it will be removed from radarr and the file will be deleted from disk.
I haven’t, but it looks like I’ve got another exporter to install and dashboard to create 😁
Not a whole lot to be honest. But I work with OpenTelemetry everyday for my day job, so it was a little exercise for me.
Though, OTEL does have some advantages in that It is a vendor agnostic collection tool. allowing you to use multiple different collection methods and switch out your backend easily if you wish.
Prometheus for metrics
Loki for logs
Grafana for dashboards.
I use node exporter for host metrics (Proxmox/VMs/SFFs/RaspPis/Router) and a number of other *exporters:
I use the OpenTelemetry collector to collect some of the above metrics, rather than Prometheus itself, as well as docker logs and other log files before shipping them to Prometheus/Loki.
Oh, I also scrape metrics from my Traefik containers using OTEL as well.
This is fixed in the latest version, 0.0.35
I have pretty much this exact setup.
That being said, all of the configs are stored in a private git repo that isn’t exposed to the internet, so I’m afraid I can share it all with you.
Like others, I don’t use a UI for Flux, just a combination of VSCode, Vim, kubectl, k9s and the flux cli.
Kubernetes is not for the faint hearted and is a massive step up/learning curve from Docker. I definitely wouldn’t recommend it for everyone, I’m ‘lucky’ that I also work with it most of the time in my day job.
I can share my immich helm release later, but I’d suggest looking into bjw-s-app template and having a look at https://kubesearch.dev/