The PriorityClasses exist in the repository but no pod uses them, so every platform pod still evicts at priority 0. Attach platform-critical to Keycloak (CR spec.scheduling) and Gitea (chart priorityClassName), and platform-low to Loki (singleBinary) and Tempo. The Keycloak CR also gets spec.image at the running 26.7.0 digest with startOptimized: false: with spec.image the operator otherwise assumes a pre-built optimized image, and this is the stock one. Grafana and pgAdmin have no top-level priorityClassName in their charts and are left for later; platform-postgres is W1's file and tech-log belongs to its deploy/ directory. Risk: applying restarts Keycloak, Gitea, Loki and Tempo once, so it belongs in the k3s restart window, after the PriorityClasses exist (a pod that names a missing class is rejected). The accepted-drift list holds these objects until 2026-11-30. Verification (desktop): render-phase1/2 and render-observability-core pass with the four priorityClassName values; kubectl diff (server dry-run) against live shows only these fields.
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.