<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitOps on Szymon Kocur</title><link>https://szymonkocur.com/tags/gitops/</link><description>Recent content in GitOps on Szymon Kocur</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 28 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://szymonkocur.com/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>Flux vs HPA: Stop GitOps From Fighting Your Replica Count</title><link>https://szymonkocur.com/posts/flux-ignore-differences-hpa-replica-count/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://szymonkocur.com/posts/flux-ignore-differences-hpa-replica-count/</guid><description>&lt;p&gt;I added a Horizontal Pod Autoscaler to a Flux-managed Deployment and watched the replica count bounce between what the HPA wanted and what Git said. Every few minutes, Flux would reconcile, see that &lt;code&gt;spec.replicas&lt;/code&gt; had drifted from the Git state, and reset it. The HPA would immediately scale it back. Repeat forever.&lt;/p&gt;
&lt;p&gt;This is a fundamental tension in GitOps: Flux&amp;rsquo;s job is to make the cluster match Git. The HPA&amp;rsquo;s job is to set the replica count based on metrics. They both write to the same field, and they disagree.&lt;/p&gt;</description></item></channel></rss>