Files
DongHyeonka d92dc5d163 feat(observability): read node-exporter textfile metrics
The host timers from the k3s maturity work (last Gitea dump and k3s
datastore backup, live drift count, API server and kubelet certificate
expiry) write their results as *.prom files. node-exporter does not
read any textfile directory, so Prometheus never sees them.

Pass --collector.textfile.directory pointing at
/var/lib/node_exporter/textfile_collector under the read-only host
root mount the chart already has. No volume is added. The host
installer creates the directory; until then the collector only
reports an error metric.

Verification: helm template of prometheus-node-exporter 4.56.1 with
these values renders the argument next to --path.rootfs=/host/root.
2026-11-12 07:29:48 +09:00
..

Observability core

This root composes the internal observability workloads deployed after the namespace, CRD, and Local PV prerequisites:

  • kube-prometheus-stack without Grafana or its bundled node-exporter;
  • single-binary Loki and Tempo using isolated AIStor buckets;
  • Alloy for Pod logs and internal OTLP/gRPC traces;
  • a standalone node-exporter;
  • the exact core NetworkPolicy matrix, platform rules, scrape targets, verified dashboards, and source-only Alertmanager Slack routing.

It intentionally does not create public ingress, Grafana, OIDC, or credential Secrets. The Slack routing source references alertmanager-slack-webhook/url; while that Secret is absent, do not apply the AlertmanagerConfig, its kube-prometheus-stack reference, its public HTTPS NetworkPolicy, or alert rules. Namespace, CRD, and Local PV roots remain outside this aggregate because their protected apply order is different.