<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Argocd on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/argocd/</link>
    <description>Recent content in Argocd on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/argocd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted GitOps Container Image Update Automation: ArgoCD Image Updater vs Flux Image Automation vs Renovate (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-gitops-container-image-update-automation-argocd-flux-renovate-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-gitops-container-image-update-automation-argocd-flux-renovate-guide/</guid>
      <description>&lt;p&gt;In a GitOps workflow, your Kubernetes manifests live in Git and drive cluster state. But what happens when a new container image is built? Manually updating image tags in Git is error-prone and slow. This guide compares three tools that automate container image updates in GitOps pipelines: &lt;strong&gt;ArgoCD Image Updater&lt;/strong&gt;, &lt;strong&gt;Flux Image Automation&lt;/strong&gt;, and &lt;strong&gt;Renovate for Container Images&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
