This is an example deployment intended for demonstration and learning purposes only. It is not hardened, audited, etc.
Example GitOps repository for Firework, focused on building Firecracker-ready rootfs images and publishing them to S3 and GCS. Both x86 and ARM64 images are built and published, to one bucket per cloud, under an <arch>/ key prefix. The Firework agent reads the prefix matching the node it runs on, so a single bucket serves a mixed-architecture fleet.
- firework - orchestrator runtime (
firework-agent,enricher,scheduler) - firework-deployment-example - Terraform + Packer deployment on AWS and GCP
Service/config semantics are documented in the main firework repository:
- Configuration reference: https://github.com/artemnikitin/firework/tree/main/docs/configs
- Architecture details: https://github.com/artemnikitin/firework/tree/main/docs/architecture
This repository intentionally keeps only high-level pipeline guidance.
Persistent-volume defaults are present in defaults.yaml.
tenants/tenant-1/elasticsearch.yaml mounts its data directory from a local
persistent volume. Tenant-1 Kibana and all tenant-2 and tenant-3 services
remain stateless. Enable and verify the local storage pool on every AWS and
GCP node before merging this configuration.
CI builds and publishes these images automatically on every push to main
(plus pull requests, a weekly schedule, and manual dispatch). See
docs/ci-pipeline.md for triggers, incremental-build
behavior, and bucket configuration.