Releases: Element84/filmdrop-k8s-tf-modules
v1.1.0
v1.0.0
First release for the FilmDrop on K8s terraform modules
We have released several terraform modules to install components that will be needed to support the infrastructure required to deploy the STAC Workflow Open Orchestration Platform (SWOOP).
Linkerd
The local development environment includes Linkerd as a service mesh. More information is available here.
You can configure whether or not Linkerd is included in deployment by setting the deploy_linkerd
flag in the inputs file.
Nginx ingress proxy
An nginx ingress proxy has been added by default to the local development environment More information is available here.
You can configure whether or not Ingress NGINX is included in deployment by setting the deploy_ingress_nginx
flag in the inputs file.
Monitoring
The local development environment includes resources for aggregating and visualizing logs and metrics. This includes:
- Grafana for visualization and dashboards. You can configure whether or not grafana is included in deployment by setting the
deploy_grafana_prometheus
flag in the inputs file. - Prometheus for metric monitoring. You can configure whether or not prometheus is included in deployment by setting the
deploy_grafana_prometheus
flag in the inputs file. - Loki for log storage and disovery. You can configure whether or not loki is included in deployment by setting the
deploy_loki
flag in the inputs file. - Promtail for log scraping. You can configure whether or not loki is included in deployment by setting the
deploy_promtail
flag in the inputs file.
More information is available here.
IO
The IO module includes MinIO, an S3 compatible object storage for the usage of the SWOOP API, SWOOP Caboose, and SWOOP Conductor. More information is available here.
You can configure whether or not STAC-FastAPI is included in deployment by setting the deploy_minio
flag in the inputs file.
DB
The DB module includes PostgreSQL, an open source object-relational database system for the usage of the SWOOP API, SWOOP Caboose, and SWOOP Conductor. More information is available here.
You can configure whether or not Postgres is included in deployment by setting the deploy_postgres
flag in the inputs file.
The DB module also has a configurable swoop-db-init which will initialize swoop-db with the creation of a SWOOP database and Roles for each SWOOP Component. You can configure whether or not swoop-db-init is included in deployment by setting the deploy_db_init
flag in the inputs file.
STAC-FastAPI
The local development environment includes a module for deploying STAC-FastAPI, which provides an API that exposes a STAC catalog that is persisted in a backend Postgres database with its component STAC Collections and Items. More information is available here.
You can configure whether or not STAC-FastAPI is included in deployment by setting the deploy_stacfastapi
flag in the inputs file.
SWOOP
The swoop module contains the SWOOP Bundle which will install the followin the following components into a kubernetes cluster:
- swoop-api - configure whether or not SWOOP-API is included in deployment by setting the
deploy_swoop_api
flag in the inputs file - argo-workflows - configure whether or not Argo Workflows is included in deployment by setting the
deploy_argo_workflows
flag in the inputs file - swoop-caboose - configure whether or not SWOOP Caboose is included in deployment by setting the
deploy_swoop_caboose
flag in the inputs file - swoop-conductor - configure whether or not SWOOP Conductor is included in deployment by setting the
deploy_swoop_conductor
flag in the inputs file
The SWOOP Bundle is inteded to group all SWOOP components compatible with the same database schema version and it's related migration operations. More information is available here.
The SWOOP Bundle also has a configurable swoop-db-migration which will migrate forward or backwards a schema version of the swoop-db in support of the SWOOP Components. You can configure whether or not swoop-db-migration is included in deployment by setting the deploy_db_migration
flag in the inputs file.
Tiling
The local development environment includes resources for rendering and serving tiles. More information is available here.
Currently Titiler does not distribute a docker image for an ARM architecture. If you're running an Apple silicon (M1, M2) or similar machine you should skip installation of the tiling namespace.
You can configure whether or not tiling resources are included in deployment by setting the deploy_tiling
flag in the inputs file.
Profiles
To view and extend profiles, head here.
flop CLI
flop
is a utility for creating and interacting with FilmDrop-on-K8s test environments. The name is a portmanteau of FiLmdrOP.