Graham McIntire
4fefb81c24
Phase 3 Stream C Rust side. Completes the HrrrFetchWorker port. Pipeline: - db::claim_next_hrrr_task — FOR UPDATE SKIP LOCKED on hrrr_fetch_tasks, newest valid_time first. Accepts the points JSONB directly. - hrrr_points::process_batch — fetch surface + pressure GRIB2 once per task (tokio::try_join), decode via the existing wgrib2 plumbing, then for each requested point pull the cell and UPSERT INTO hrrr_profiles (conflict on lat/lon/valid_time). - db::complete_hrrr_task / fail_hrrr_task — status transitions; Elixir backfill re-enqueues failed rows on next /30-min scan. Shipping pieces: - new bin src/bin/hrrr_point_worker.rs - new module src/hrrr_points.rs (process_batch, upsert_profile) - new Cargo [[bin]] entry; Dockerfile builds both binaries in one stage and ships them in the runtime image so a single CI pipeline covers the whole cluster - k8s/deployment-hrrr-point-rs.yaml (1 replica, 1 Gi limit, anti-affinity against prop-grid-rs so chain + point work don't fight for wgrib2 slots). Uses the same image; command: override picks the right binary. - kustomization.yaml: include the new deployment so flux applies it - deployment-grid-rs.yaml: bump readiness initialDelaySeconds 3→15 + failureThreshold 3→6 so a slow DB connect during startup can't race the first probe 119 Rust tests green.
14 lines
486 B
YAML
14 lines
486 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
# secret.yaml is applied out-of-band and is git-ignored (contains plaintext
|
|
# credentials). Flux reconciles deployment.yaml etc. but does NOT manage the
|
|
# secret. Rotate secrets by applying secret.yaml with kubectl directly.
|
|
resources:
|
|
- namespace.yaml
|
|
- rbac.yaml
|
|
- deployment.yaml
|
|
- deployment-backfill.yaml
|
|
- deployment-grid-rs.yaml
|
|
- deployment-hrrr-point-rs.yaml
|
|
- service.yaml
|
|
- metrics-service.yaml
|