Towards Greener Deployment: Assessing Energy Efficiency i...
summary
Compares energy of two pipelines by deploying the same sample app on a Minikube cluster while exporting pod power metrics with Kepler and scraping with Prometheus and Grafana, using Argo CD (GitOps) vs GitHub Actions runners via the actions-runner-controller. Argo CD idles around 1 W, spikes at the first deploy then sits near ~35 W for the hour; GitHub Actions idles lower but shows higher peak consumption during deploys; Argo H‑spoke (multi‑cluster) uses almost twice the energy of standalone.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:26Context
- 1:03Deployment Tools
- 2:14Why Kler
- 3:09Test Setup
- 4:02Experimental Conditions
- 6:21Architectures
- 7:27Conclusion
- 7:52Outro
related talks
31mEvaluating the Energy Footprint of GitOps Architectures: A Benchmark Analysis
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
43mGitOps at Scale with and Argo CD on
13mPerformance and Energy Efficiency in Docker
28mMore Data Please: Hands on Green Cloud Experiments
26mDog Food Delight: How Argo Workflows Eats Its Own CI
06mSponsored Keynote: Argo CD vs the World
42mRevolutionize Your Deployment Pipeline