Simplifying Edge Deployments Using EMCO and GitOps
summary
EMCO writes rendered Helm charts and cloud-specific Kustomize/Flux/RootSync files into per-cluster git branches and uses Flux v2 agents to pull those repos; demo shows three clusters (direct, Flux-managed, Azure Arc) receiving apps and later being fully deleted from git and cluster state. Integration supports Flux v2, Azure Arc, Anthos, uses a bundled Gitea or external git, keeps credentials inside clusters and uses HTTPS and token-based auth so EMCO acts as an intelligent agent for placement, customization and consistent GitOps deployments.
AI-written summary · about
chapters (8)
- 0:00EMCO and GitOps intro
- 1:06Edge deployment problems
- 5:45EMCO for edge orchestration
- 7:51EMCO flow with GitOps
- 11:24GitOps backend in EMCO
- 12:30EMCO’s Git server benefits
- 13:35Solving deployment complexities
- 18:30Live demo: EMCO with GitOps
related talks
29mAccelerating GitOps Adoption with Flux
24mHosting Applications in the Real World
20mGitOps Modern Operations for EKS
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux
39mEnhance Your Kubernetes Experience with GitOps & Flux
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
32mManaging Helm Deployments with Gitops at CERN