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.
This commit is contained in:
@@ -80,6 +80,8 @@ loki:
|
||||
max_compaction_parallelism: 1
|
||||
|
||||
singleBinary:
|
||||
# services/priority-classes: logs can be lost first under node pressure.
|
||||
priorityClassName: platform-low
|
||||
replicas: 1
|
||||
sidecar: false
|
||||
podLabels:
|
||||
|
||||
@@ -4,6 +4,9 @@ global:
|
||||
|
||||
replicas: 1
|
||||
|
||||
# services/priority-classes: traces can be lost first under node pressure.
|
||||
priorityClassName: platform-low
|
||||
|
||||
config: |
|
||||
stream_over_http_enabled: false
|
||||
memberlist:
|
||||
|
||||
Reference in New Issue
Block a user