https://blog.landryzetam.net/tags/fluxcd/Recent content in FluxCD on Landry Zetam - Tech BlogHugo -- gohugo.ioen-usSun, 21 Dec 2025 00:00:00 +0000https://blog.landryzetam.net/posts/gitops-framework/Sun, 21 Dec 2025 00:00:00 +0000https://blog.landryzetam.net/posts/gitops-framework/<h2 id="overview">Overview</h2> <p>The Fako Cluster uses a GitOps approach where <strong>Git is the single source of truth</strong> for all cluster state. Every deployment, configuration change, and infrastructure update flows through Git commits. FluxCD watches the repository and automatically reconciles the cluster to match the desired state defined in code.</p> <p>This post explains the repository structure, the reasoning behind each directory, and how the pieces work together.</p> <h2 id="repository-structure">Repository Structure</h2> <pre tabindex="0"><code>fako-cluster/ ├── apps/ # Application deployments │ ├── base/ # Base Kustomize configurations │ └── staging/ # Environment overlay (what actually deploys) ├── clusters/ # Cluster bootstrap and Flux config │ └── staging/ # Flux Kustomizations that orchestrate everything ├── infrastructure/ # Platform components │ ├── controllers/ # Operators (Cert-Manager, CloudNative-PG, etc.) │ └── configs/ # Configuration for controllers ├── monitoring/ # Observability stack │ ├── controllers/ # Prometheus, Loki, Grafana, etc. │ └── configs/ # Dashboards, alerting rules ├── scripts/ # Deployment and maintenance scripts └── notes/ # Documentation and troubleshooting </code></pre><h2 id="the-basestaging-pattern">The Base/Staging Pattern</h2> <p>The most important concept to understand is the <strong>base/staging pattern</strong> used throughout the repository.</p>https://blog.landryzetam.net/posts/secrets-management-with-sops-flux-gitops/Thu, 07 Aug 2025 00:00:00 +0000https://blog.landryzetam.net/posts/secrets-management-with-sops-flux-gitops/<h2 id="the-problem-secrets-in-gitops">The Problem: Secrets in GitOps</h2> <p>When I started my Kubernetes homelab journey, I quickly hit a wall that every GitOps practitioner faces: <strong>How do you store secrets in Git without compromising security?</strong></p> <p>The GitOps philosophy is beautifully simple - everything should be in Git. Your entire cluster state, all your applications, configurations, and yes, even secrets. But committing passwords, API keys, and certificates to a public (or even private) repository feels fundamentally wrong. It is wrong.</p>https://blog.landryzetam.net/posts/gitops-with-fluxcd/Wed, 06 Aug 2025 00:00:00 +0000https://blog.landryzetam.net/posts/gitops-with-fluxcd/<p>After running the Fako Cluster for several months, I can confidently say that adopting GitOps with FluxCD has been one of the best decisions for managing my Kubernetes infrastructure. In this post, I&rsquo;ll share practical insights and patterns that have proven invaluable.</p> <h2 id="what-is-gitops">What is GitOps?</h2> <p>GitOps is a way of implementing Continuous Deployment for cloud native applications. FluxCD is designed to simplify that, making it easier than ever to manage your Kubernetes environments. Here’s why i leverage it in my workflow:</p>