<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fluxcd on Pim Widdershoven</title><link>/tags/fluxcd/</link><description>Recent content in Fluxcd on Pim Widdershoven</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/fluxcd/index.xml" rel="self" type="application/rss+xml"/><item><title>Two GitOps controllers, two layers: FluxCD for the foundation, ArgoCD for applications</title><link>/entry/gitops-fluxcd-for-the-foundation-argocd-for-applications/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>/entry/gitops-fluxcd-for-the-foundation-argocd-for-applications/</guid><description>With Talos, Cilium, Linstor, and cert-manager in place, the cluster has infrastructure but no principled way to operate it. This post adds GitOps: FluxCD for the foundation layer where ordering and simplicity matter, ArgoCD for the application layer where a UI and per-project scoping matter more. The bootstrap sequence that hands control from a script to a Git repo, the self-management property that follows, and what GitOps does not tell you about developing against it.</description></item></channel></rss>