I couldn’t summarize this in a title (even with an LLM’s help):

I wanted to:

1. Run a Tailscale service discovery agent
2. On a Tailscale node outside of the Kubernetes cluster
3. Using Podman Quadlet
4. Accessing it from the Kubernetes Cluster using the Tailscale’s egress proxy
5. Accessing the proxy with a kube-prometheus ScrapeConfig
6. In order that Prometheus would scrape the container for Tailscale client metrics

Long-winded? Yes but I had an underlying need in running the Tailscale Service Discoovery remotely and this configuration helped me achieve that.

Spent time today yak-shaving which resulted in an unplanned migration from MicroK8s ‘prometheus’ add-on to the new and not fully-documented ‘observability’ add-on:

sudo microk8s.enable prometheus

Infer repository core for addon prometheus
DEPRECATION WARNING: 'prometheus' is deprecated and will soon be removed. Please use 'observability' instead.
...

The reason for the name change is unclear.

It’s unclear whether there’s a difference in the primary components that are installed too (I’d thought Grafana wasn’t included in ‘prometheus’), (Grafana) Loki and (Grafana) Tempo definitely weren’t included and I don’t want them either.