helm-osrm-backend/templates
Mathias Beaulieu-Duncan 8576172bb4 Remove in-cluster data processing; serve pre-built OSRM data from PVC
The init containers downloaded the OSM extract and ran
osrm-extract/partition/customize on every pod start. extract peaks ~4GB+
RAM, which OOM-kills on the 4GB nodes whenever the pod restarts (it only
survived 306 days by never restarting). Removed both init containers.

Routing data (map.osrm.*) is now built OUTSIDE the cluster and loaded
onto the PVC directly. Bumped chart to 0.2.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-03 17:11:04 -04:00
..
tests initial commit 2025-02-18 14:39:05 -05:00
_helpers.tpl initial commit 2025-02-18 14:39:05 -05:00
deployment.yaml Remove in-cluster data processing; serve pre-built OSRM data from PVC 2026-06-03 17:11:04 -04:00
hpa.yaml initial commit 2025-02-18 14:39:05 -05:00
ingress.yaml initial commit 2025-02-18 14:39:05 -05:00
NOTES.txt initial commit 2025-02-18 14:39:05 -05:00
pvc.yaml initial commit 2025-02-18 14:39:05 -05:00
service.yaml initial commit 2025-02-18 14:39:05 -05:00
serviceaccount.yaml initial commit 2025-02-18 14:39:05 -05:00