# OSM on postgres

## Key components
- a stable, completely standardized database that can easily be scaled backed by postgres + postgis
    - this is backed a by a persistent, node-independent storage claim
- a specialized container (running as cronjob/on demand job) that ingests the data from OSM dumps.
    - this is backed by its own storage to prevent excessive re-downloads


## Prerequisites
- A storage class provisioner
- A CNPG operator that will provision this.


## Results
A well defined database with a table and entries defined [base/importer.configmap.yaml](base/importer.configmap.yaml) that can be reached from within the cluster.
- Acccess data can be read from the secret `<postgres-cluster-name>-app`.