prop/k8s
Graham McIntire c9aa9c53d5
ops: prop deployment floor at 2 replicas, surge to 4
A single-pod floor meant any pod restart (rolling deploy mid-run,
OOM kill, node drain) took the whole site down for the boot window.
Bump HPA to minReplicas: 2 / maxReplicas: 4 so the floor is HA and
load surges (LiveView traffic coinciding with the hourly propagation
chain) still get headroom. Combined with the existing rolling-update
strategy (maxSurge: 1, maxUnavailable: 0) this means deploys go
2 -> 3 -> 2 with zero downtime.
2026-05-03 15:06:37 -05:00
..
deployment-backfill.yaml remove obsolete flux manifest and imagepolicy annotations 2026-04-29 11:00:05 -05:00
deployment-grid-rs.yaml remove obsolete flux manifest and imagepolicy annotations 2026-04-29 11:00:05 -05:00
deployment-hrrr-point-rs.yaml remove obsolete flux manifest and imagepolicy annotations 2026-04-29 11:00:05 -05:00
deployment.yaml ops: prop deployment floor at 2 replicas, surge to 4 2026-05-03 15:06:37 -05:00
hpa.yaml ops: prop deployment floor at 2 replicas, surge to 4 2026-05-03 15:06:37 -05:00
kustomization.yaml infra(k8s): load-based HPAs, drop anti-affinity, retire talos5 2026-04-23 18:43:18 -05:00
metrics-service.yaml feat(k8s): NodePort service for external Prometheus scraping 2026-04-18 16:51:46 -05:00
namespace.yaml Add k8s manifests and Forgejo CI for cluster deployment 2026-04-06 09:25:24 -05:00
rbac.yaml Add Erlang clustering via libcluster and expose LiveDashboard 2026-04-06 09:46:48 -05:00
service.yaml fix(k8s): tier label isolates hot pods from backfill endpoints 2026-04-19 16:58:13 -05:00