<?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 Thinx-Tank</title><link>https://blog.thinxai.net/tags/gitops/</link><description>Recent content in GitOps on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Is the Control Plane</title><link>https://blog.thinxai.net/posts/git-is-the-control-plane/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/git-is-the-control-plane/</guid><description>&lt;p&gt;Earlier this month &lt;a href="https://medium.com/google-cloud/gitops-for-ai-agents-on-google-cloud-argocd-config-sync-and-gke-03fdad8b0716"&gt;Neel Shah wrote up his pattern&lt;/a&gt; for running AI agents on GKE with GitOps. The core of the piece is a repo layout where an agent&amp;rsquo;s system prompt, tool allowlist, model binding, and guardrail config all live as versioned files, and a reconciler (ArgoCD or Config Sync) continuously forces the live cluster to match. A prompt tweak is a one-line diff. Rollback is a git revert. A policy engine blocks a dangerous tool grant before it lands.&lt;/p&gt;</description></item></channel></rss>