Files
DongHyeonka de600a0bb1 feat(priority): attach PriorityClasses to Keycloak, Gitea, Loki, Tempo
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.
2026-11-12 01:25:24 +09:00
..

Tempo

This root renders grafana-community/tempo chart 2.2.3 as one Tempo 2.10.7 StatefulSet in observability.

  • The image is rewritten to the reviewed amd64 digest.
  • Traces use the tempo AIStor bucket through tempo-object-storage; no root credential is referenced.
  • Retention is seven days. WAL and local working data use the dedicated 5Gi Retain Local PV.
  • Only the query/metrics port 3200 and OTLP/gRPC port 4317 are exposed.
  • OTLP/HTTP, Jaeger, Zipkin, metrics-generator, and tempo-query are disabled.

Do not delete the PVC or bucket during rollback. Stop the StatefulSet and preserve its Retain volume while S3/WAL state is investigated.