On 2026-11-11 the desktop booted with the RTC read as UTC while it held KST, so the clock ran 9 hours ahead until NTP pulled it back. Prometheus had written one hour of samples stamped 18:36-19:36Z into its TSDB head during that window. With outOfOrderTimeWindow at the chart default of 0s, every later scrape was older than the head's valid range and was dropped as "out of bounds". From 11:21Z no metric was stored, no rule could fire on real data, and KubeAPIDown (an absent() rule) fired falsely. It would have stayed blind until the wall clock passed the bogus head time, about 7 hours later. Set prometheusSpec.tsdb.outOfOrderTimeWindow to 10h. Samples up to 10 hours behind the head are now accepted, which covers the +9h KST-as-UTC misread. The README records why. Rejected: deleting the head WAL from the Retain PV. It works at once but removes persisted data and needs the pod stopped. Rejected: waiting for the clock to catch up. It leaves monitoring blind for hours during the period when the cause of the incident is still being found. Risk: out-of-order samples use an extra in-memory head and vertical compaction only while they arrive; in normal operation none arrive. A genuinely late exporter could now backfill up to 10h, which is harmless on this single-node Prometheus. Preventing the clock jump itself is the host change in infrastructure/host, not this commit. Verification: the values file parses and holds prometheus.prometheusSpec.tsdb.outOfOrderTimeWindow=10h. The live Prometheus CR already carried tsdb.outOfOrderTimeWindow=0s from this chart key, so the key maps to spec.tsdb. The same value was patched onto the live CR: the operator wrote out_of_order_time_window: 10h, the config reloaded at 13:04:37Z, "too old" warnings dropped to 0, all 34 targets report up, and KubeAPIDown resolved. The pinned renderer (scripts/validate/render-observability-core.sh) was not run: it requires Helm v3.19.4 and kustomize v5.8.1, which are not installed on the laptop or the desktop.
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.