- Notifications
You must be signed in to change notification settings - Fork6
☸️🐋 GitOps Flux-based adsb.lol infrastructure - kubernetes, readsb, tar1090, mlat-server, api, history
License
adsblol/infra
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the adsb.lol infrastructure.It aims to aggregateADS-B &MLAT
The repo should contain everything for you to be able to run a copy of this service.
Due to recent events regarding ADSBExchange being acquired, it would be wise for the community to have a quick and easy way to deploy an alternative aggregation service.
Right now, the infrastructure's entrypoint is meant to bemanifests/default
You can see what manifests would end up on the cluster by doingkustomize build manifests/default
.
Should you need to copy this for your own infrastructure, an understanding of Kubernetes and Kustomize is recommended.
Thebases
folder contains basic Kubernetes components. These will be reused later.
Running wiedehopf's mlat-server
Running wiedehopf's readsb
Themanifests
folder is closer to the expected state of the cluster.
Everything is inherited from a component inbases
and then patched as necessary.
This is meant to be the publicly accessible ingest readsb. Can be scaled if needed.
This reasdb sends data to the hub readsb
This is a pattern you will see throughout this repo.
The general idea is thatbase
inherits, or defines a basic deployment of the application.
The general idea is thatdefault
has the patches for this service to be configured properly.This would include any environment variables, etc.
Runs mlat-server
A copy of readsb aggregating ingest data
This readsb sends data to the planes readsb
A copy of readsb, with its tar1090 instance exposed to the public.
Global (to the namespace) resources such as publicly-intended services and ingresses, NetworkPolicies.
user -> ingest -> hub -> planes
ingest -> mlat -> hub -> planes