Lightning Talk: Pushing GitOps To the Edge (Literally)
summary
Argo CD keeps desired state but loses that guarantee when clusters go offline; this solution mirrors upstream repos to a git mirror colocated with Argo, bundles and pushes required images into a local registry using Zarf and Crane, and enforces a pre-sync hook that verifies manifest revisions and image bundles exist before allowing a sync. K3s persists cluster state to disk so rollbacks and offline syncs succeed even across restarts, enabling reliable GitOps in high-latency or airgapped edge sites.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:43Argo CD in cloud environments
- 1:45Kubernetes at the edge challenges
- 3:51Argo CD offline problems
- 5:13Argo CD cluster changes
- 6:36Sync steps to prevent failures
- 7:17Local Git and image bundle
- 9:23Innovation at the edge
related talks
31mLeveraging GitOps to wrangle your clusters and projects
36mKEYNOTE: Taking a step back and leveraging GitOps to wrangle your clusters and projects
30mManage your kubernetes cluster in the GITOPS way !!
26mGitOps: yea or nay?
13mHow GitOps Should I Be? Lessons from a Kinda-GitOps Environment
27mImplementing GitOps with ArgoCD: A Practical Guide
25mGit Sh*t Done, the GitOps Way
01h 19mTutorial: Everything You Need To Become a GitOps Ninja