Flux. The GitOps operator for Kubernetes¶

Networking and Security¶

Service Mesh and Gateway¶

Envoy¶

• (2022) solo.io: The 3 best ways to use Flux and Flagger for GitOps with your Envoy Proxy API gateways [MARKDOWN CONTENT] [ADVANCED LEVEL] 🌟🌟🌟🌟 [ENTERPRISE-STABLE] — Outlines integration patterns for orchestrating progressive delivery at the ingress boundary using Flux, Flagger, and Envoy-based gateways. Evaluates traffic-shifting methodologies including canary deployments, A/B testing, and blue-green releases. Live Grounding confirms Envoy-based ingress traffic shaping remains the de facto method for automated canary analysis in cloud-native topologies.

Platform Engineering¶

GitOps and Deployment¶

Flux Ecosystem¶

• (2026) github: Flux Version 2 ⭐ 8186 [GO CONTENT] 🌟🌟🌟🌟🌟 [DE FACTO STANDARD] — The official active repository for Flux v2. Rebuilt from the ground up as a set of Kubernetes controllers (GitOps Toolkit) to allow decoupled, highly parallel reconciliation of Git configurations.
• (2021) github: Flux ⭐ 6861 [GO CONTENT] 🌟🌟🌟🌟🌟 [DE FACTO STANDARD] [LEGACY] — The deprecated and archived GitHub repository for the original Flux v1 GitOps engine. Completely succeeded by the microservice-driven, decoupled Flux v2 architecture.
• (2026) Flux [GO CONTENT] [COMMUNITY-TOOL] — The main ecosystem page for Flux, a CNCF Graduated tool designed for GitOps continuous delivery. Keeps Kubernetes clusters synchronized with version-controlled repositories, supporting declarations via Helm, Kustomize, and native YAML.
• (2026) toolkit.fluxcd.io: GitOps Toolkit 🌟 [GO CONTENT] [COMMUNITY-TOOL] — Highlights the modular architecture of Flux v2 (source-controller, kustomize-controller, helm-controller, notification-controller). Allows platform teams to customize GitOps engines using dedicated custom resource definitions.
• (2025) docs.microsoft.com: Configurations and GitOps with Azure Arc enabled Kubernetes [NONE CONTENT] [DOCUMENTATION] [COMMUNITY-TOOL] — Microsoft's guide to deploying enterprise multi-cluster configurations using Azure Arc integrated with Flux v2 GitOps extensions. Enables unified policy-driven application deployment across hybrid cloud estates.
• (2022) thenewstack.io: GitOps at Home: Automate Code Deploys with Kubernetes and Flux [YAML CONTENT] [COMMUNITY-TOOL] — A practical walkthrough for setting up self-hosted GitOps pipelines on homelabs or small clusters using Flux. Highlights automated deployment routines and resource orchestration.
• (2021) docs.fluxcd.io [NONE CONTENT] [DOCUMENTATION] [LEGACY] — Archived reference documentation for the legacy Flux v1 orchestrator. Left online purely as historical reference; teams must use modern Flux v2 systems for controller architectures and security controls.
• (2021) blog.sldk.de: Introduction to GitOps on Kubernetes with Flux v2 🌟 [NONE CONTENT] [COMMUNITY-TOOL] — A clear introduction to the fundamental architecture of Flux v2. Explains key resources including GitRepository, Kustomization, and how they combine to deploy reliable workloads.
• (2020) alicegg.tech: Managing a Kubernetes cluster with Helm and FluxCD [NONE CONTENT] [COMMUNITY-TOOL] — Detailed architectural analysis of managing Helm releases within Flux GitOps pipelines. Explores automated release upgrades, HelmRepository declarations, and rollback mechanisms.

Storage and Databases¶

Cloud-Native Storage¶

Stateful GitOps¶

• (2022) thenewstack.io: Deploy Stateful Workloads on Kubernetes with Ondat and FluxCD [MARKDOWN CONTENT] [ADVANCED LEVEL] 🌟🌟🌟 [COMMUNITY-TOOL] — Explores deploying resilient, stateful microservices using Ondat (formerly StorageOS) as a persistent software-defined storage layer combined with Flux for deployment state synchronization. Live Grounding notes that while Ondat offered advanced CSI-driven capabilities, consolidation in the cloud-native storage sector has shifted focus toward alternatives like Longhorn, Rook/Ceph, or cloud-managed block storage.

💡 Explore Related: Jenkins | Tekton | Argo

🔗 See Also: About | Postman