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:
@@ -2,6 +2,9 @@ namespace: gitea
|
||||
|
||||
replicaCount: 1
|
||||
|
||||
# services/priority-classes: evicted after everything that is not critical.
|
||||
priorityClassName: platform-critical
|
||||
|
||||
image:
|
||||
registry: docker.gitea.com
|
||||
repository: gitea
|
||||
|
||||
@@ -9,6 +9,15 @@ metadata:
|
||||
spec:
|
||||
instances: 1
|
||||
|
||||
# The 26.7.0 server image running on 2026-11-12, by digest. With spec.image set
|
||||
# the operator assumes a pre-built (optimized) image; this is the stock image,
|
||||
# so startOptimized stays false and Keycloak builds at start as before.
|
||||
image: quay.io/keycloak/keycloak@sha256:0f198be292568439d700cdbfb893e69a6009bb43a94a06a945b1d3d506c76b13
|
||||
startOptimized: false
|
||||
|
||||
scheduling:
|
||||
priorityClassName: platform-critical
|
||||
|
||||
db:
|
||||
vendor: postgres
|
||||
host: platform-postgres-rw.platform-data.svc.cluster.local
|
||||
|
||||
@@ -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:
|
||||
|
||||
@@ -6,13 +6,14 @@
|
||||
|
||||
| 이름 | 값 | 선점 | 붙일 곳 |
|
||||
| --- | --- | --- | --- |
|
||||
| `platform-critical` | 1000000 | 낮은 것을 선점 | platform-postgres, Gitea, Keycloak, tech-log |
|
||||
| `platform-low` | -1000 | 선점 안 함 | Grafana, pgAdmin, Loki, Tempo |
|
||||
| `platform-critical` | 1000000 | 낮은 것을 선점 | Gitea(`services/gitea` values), Keycloak(CR `spec.scheduling`). platform-postgres는 W1, tech-log는 tech-log `deploy/` |
|
||||
| `platform-low` | -1000 | 선점 안 함 | Loki(`singleBinary`), Tempo. Grafana·pgAdmin은 chart에 최상위 키가 없어 아직 안 붙였다 |
|
||||
|
||||
- 아무것도 안 붙인 파드는 기본값 0이다. 시스템 클래스(`system-*`, 20억)는 그대로 가장 높다.
|
||||
- `globalDefault`는 둘 다 끈다. 새 파드가 모르게 우선순위를 얻지 않게 하려는 것이다.
|
||||
- 클래스를 만드는 것은 아무 파드도 바꾸지 않는다. **붙이는 것은 파드 재시작을 부르므로**
|
||||
k3s 재시작 창에 한다(`infrastructure/host/k3s/README.md`).
|
||||
k3s 재시작 창에 한다(`docs/runbooks/k3s-restart-window.md`).
|
||||
- **클래스를 먼저 만든다.** 없는 클래스를 가리키는 파드는 생성이 거절돼 Deployment가 새 파드를 못 만든다.
|
||||
|
||||
```sh
|
||||
kubectl apply -k services/priority-classes
|
||||
|
||||
Reference in New Issue
Block a user