GitOpsCon North America 2022

Multi-cluster, multi-app edge deployments may involve multiple applications on different cluster types located in different environments. This adds complexity to management, security, and consistency. These complexities can be addressed by using EMCO (Edge Multi-Cluster Orchestrator). With EMCO, GitOps can be leveraged to communicate with Kubernetes clusters over the git protocol, integrating with a variety of public clouds. EMCO acts as the intelligent agent that writes resources to the git location, helping in management, consistency, and security (since no direct communication happens to these clusters). - What goes in the repository: o Kubernetes resources as rendered from Helm Charts. o Cloud-specific configuration and resource files (Kustomization, FluxCD system files, RootSync configurations). - Security considerations: o Token-based authentication for Flux, Azure and Anthos. o Kubernetes Secrets concept for storing and passing sensitive information. o HTTPS APIs ensure data privacy. - The different git libraries in use (and future): o Git2go for interacting with git. o Azure and Anthos APIs o Gitea for local git server