feat: expose flux observability services over tailscale
This commit is contained in:
@@ -217,7 +217,7 @@ Ansible `site.yml` now skips `observability` and `observability-content` roles b
|
||||
|
||||
## Observability Stack
|
||||
|
||||
The Ansible playbook deploys a lightweight observability stack in the `observability` namespace:
|
||||
Flux deploys a lightweight observability stack in the `observability` namespace:
|
||||
|
||||
- `kube-prometheus-stack` (Prometheus + Grafana)
|
||||
- `loki`
|
||||
@@ -225,7 +225,7 @@ The Ansible playbook deploys a lightweight observability stack in the `observabi
|
||||
|
||||
Grafana content is managed as code via ConfigMaps in `infrastructure/addons/observability-content/` (Flux), migrated from `ansible/roles/observability-content/`.
|
||||
|
||||
Services are kept internal by default, with optional declarative Tailscale exposure when the Tailscale Kubernetes Operator is healthy.
|
||||
Grafana and Prometheus are exposed via Tailscale (`loadBalancerClass: tailscale`) when the Tailscale Kubernetes Operator is healthy.
|
||||
|
||||
### Access Grafana and Prometheus
|
||||
|
||||
|
||||
Reference in New Issue
Block a user