Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/peter-evans/osrm-backend-k8s
Open Source Routing Machine (OSRM) osrm-backend for Kubernetes on Google Container Engine (GKE).
https://github.com/peter-evans/osrm-backend-k8s
canary-deployment docker-image gke google-cloud kubernetes osrm osrm-backend pbf
Last synced: 2 months ago
JSON representation
Open Source Routing Machine (OSRM) osrm-backend for Kubernetes on Google Container Engine (GKE).
- Host: GitHub
- URL: https://github.com/peter-evans/osrm-backend-k8s
- Owner: peter-evans
- License: mit
- Created: 2016-12-09T05:23:57.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2022-03-11T16:51:10.000Z (almost 3 years ago)
- Last Synced: 2024-11-02T03:11:57.758Z (3 months ago)
- Topics: canary-deployment, docker-image, gke, google-cloud, kubernetes, osrm, osrm-backend, pbf
- Language: Shell
- Homepage: https://hub.docker.com/r/peterevans/osrm-backend-k8s/
- Size: 67.4 KB
- Stars: 38
- Watchers: 7
- Forks: 24
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# osrm-backend for Kubernetes
[](https://microbadger.com/images/peterevans/osrm-backend-k8s)
[](https://circleci.com/gh/peter-evans/osrm-backend-k8s/tree/master)
Open Source Routing Machine (OSRM) [osrm-backend](https://github.com/Project-OSRM/osrm-backend) for Kubernetes on Google Container Engine (GKE).
This Docker image and sample Kubernetes configuration files are one solution to persisting [osrm-backend](https://github.com/Project-OSRM/osrm-backend) data and providing immutable deployments.
If you are looking for a more general purpose docker image, see [osrm-backend-docker](https://github.com/peter-evans/osrm-backend-docker).
## Supported tags and respective `Dockerfile` links
- [`1.21.1`, `1.21`, `latest` (*1.21/Dockerfile*)](https://github.com/peter-evans/osrm-backend-k8s/tree/master)
- [`1.20.0`, `1.20` (*1.20/Dockerfile*)](https://github.com/peter-evans/osrm-backend-k8s/tree/master/archive/1.20)
- [`1.19.0`, `1.19` (*1.19/Dockerfile*)](https://github.com/peter-evans/osrm-backend-k8s/tree/master/archive/1.19)
- [`1.18.0`, `1.18` (*1.18/Dockerfile*)](https://github.com/peter-evans/osrm-backend-k8s/tree/master/archive/1.18)
- [`1.17.1`, `1.17` (*1.17/Dockerfile*)](https://github.com/peter-evans/osrm-backend-k8s/tree/master/archive/1.17)
For earlier versions see [releases](https://github.com/peter-evans/osrm-backend-k8s/releases) and the available [tags on Docker Hub](https://hub.docker.com/r/peterevans/osrm-backend-k8s/tags/).
## Usage
The Docker image can be run standalone without Kubernetes:
```bash
docker run -d -p 5000:5000 \
-e OSRM_PBF_URL='http://download.geofabrik.de/asia/maldives-latest.osm.pbf' \
--name osrm-backend peterevans/osrm-backend-k8s:latest
```
Tail the logs to verify the graph has been built and osrm-backend is serving requests:
```
docker logs -f
```
Then point your web browser to [http://localhost:5000/](http://localhost:5000/)
## Kubernetes Deployment
The [osrm-backend](https://github.com/Project-OSRM/osrm-backend) builds a data graph from a PBF file. This process can take over an hour for a single country.
If a pod in a deployment fails, waiting over an hour for a new pod to start could lead to loss of service.
The sample Kubernetes files provide a means of persisting a data graph in storage that is used by all pods in the deployment.
Each pod having their own copy of the graph is desirable in order to have no single point of failure.
#### Explanation
Initial deployment flow:
1. Create a secret that contains the JSON key of a Google Cloud IAM service account that has read/write permissions to Google Storage.
2. Deploy the canary deployment.
3. Wait for the graph to be built and uploaded to Google Storage.
4. Delete the canary deployment.
5. Deploy the stable track deployment.
To update the live deployment with a new graph:
1. Deploy the canary deployment alongside the stable track deployment.
2. Wait for the graph to be built and uploaded to Google Storage.
3. Delete the canary deployment.
4. Perform a rolling update on the stable track deployment to create pods using the new graph.
#### Creating the secret
```bash
# Google Cloud project ID and service account details
PROJECT_ID=my-project
SA_NAME=my-service-account
SA_DISPLAY_NAME="My Service Account"
SA_EMAIL=$SA_NAME@$PROJECT_ID.iam.gserviceaccount.com
KEY_FILE=service-account-key.json
# Create a new GCP IAM service account
gcloud iam service-accounts create $SA_NAME --display-name "$SA_DISPLAY_NAME"
# Create and download a new key for the service account
gcloud iam service-accounts keys create $KEY_FILE --iam-account $SA_EMAIL
# Give the service account the "Storage Object Viewer" and "Storage Object Creator" IAM roles
gcloud projects add-iam-policy-binding $PROJECT_ID --member serviceAccount:$SA_EMAIL --role roles/storage.objectViewer
gcloud projects add-iam-policy-binding $PROJECT_ID --member serviceAccount:$SA_EMAIL --role roles/storage.objectCreator
# Create a secret containing the service account key file
kubectl create secret generic osrm-storage-secret --from-file=$KEY_FILE
```
#### Deployment configuration
Before deploying, edit the `env` section of both the canary deployment and stable track deployment.
- `OSRM_MODE` - `CREATE` from PBF data, or `RESTORE` from Google Storage.
- `OSRM_PBF_URL` - URL to PBF data file. (Optional when `OSRM_MODE=RESTORE`)
- `OSRM_GRAPH_PROFILE` - Graph profile; `car`,`bicycle` or `foot`. (Optional when `OSRM_MODE=RESTORE`)
- `OSRM_DATA_LABEL` - A meaningful and **unique** label for the data. e.g. maldives-car-20161209
- `OSRM_SA_KEY_PATH` - Path to the JSON service account key. This needs to match the `mountPath` of the volume mounted secret.
- `OSRM_PROJECT_ID` - Google Cloud project ID.
- `OSRM_GS_BUCKET` - Google Storage bucket.
## License
MIT License - see the [LICENSE](LICENSE) file for details