<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Argo-Workflows on Project Wintermute</title><link>https://wintermutecore.com/tags/argo-workflows/</link><description>Recent content in Argo-Workflows on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2026 14:00:02 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/argo-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>Argo Workflows Large Workflow Operator Notes</title><link>https://wintermutecore.com/posts/argo-workflows-large-workflow-operator-notes/</link><pubDate>Sun, 12 Jul 2026 14:00:02 +0000</pubDate><guid>https://wintermutecore.com/posts/argo-workflows-large-workflow-operator-notes/</guid><description>&lt;p&gt;&lt;a href="https://github.com/argoproj/argo-workflows"&gt;Argo Workflows&lt;/a&gt; is a Kubernetes native workflow engine that shows up often in batch data pipelines, model jobs, and internal ETL platforms. The recent activity is worth reading because it changes how large workflow status is stored, how persistence failures time out, and how the project tests a new pod layout.&lt;/p&gt;</description></item></channel></rss>