GitOps Sustainability with Flux and arm64
summary
Honeycomb migrates many services from x86 to arm64, reporting 30–40% price-performance gains and running 20–30% fewer instances while keeping latency steady; one heavy ingest service validates CPU-bound compression work. Build artifacts for both arches and use Go’s GOARCH cross-compile or multi-arch containers from CI. Start in dogfood with stateless services, shift manifests from amd64 to arm64 in Git, and use Flux + Flagger progressive delivery (requires multi-arch CI) to stage rollouts; production cutover succeeds with a small x86 Lambda fallback.
AI-written summary · about
chapters (10)
- 0:00GitOps and sustainability
- 1:04Why arm64 matters
- 4:34Honeycomb’s arm64 journey
- 9:05Migrating to arm64 at scale
- 13:41Results of arm64 migration
- 14:03GitOps with Flux explained
- 18:17Trust Flux for GitOps
- 20:45Progressive delivery with Flagger
- 21:50Demo: GitOps arm64 migration
- 27:30Q&A
related talks
06mChange Your Architecture and Save the World
29mThe Progress for Cloud Computing on Arm architecture
27mOptimizing price performance with feature management and observability (PRT259)
43mThe Green Shift: Transitioning .NET Services Across Architectures
37mWhy are multi-architecture images important?
46mArchitecting for Success and Runway
24mPlatform Engineering Is the Key Lever for Sustainable Cloud Infrastructure
16mGreen Code: Transforming DevOps for a Sustainable Future