<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/devops/</link><description>Recent content in DevOps on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>I Migrated 45 Cron Jobs into Windmill: Five Lessons from a Migration</title><link>https://blog.lynxflow.co/en/posts/windmill-cron-migration-45-jobs-2026/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/windmill-cron-migration-45-jobs-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/windmill-migration-45-2026.png" alt="Featured image of post I Migrated 45 Cron Jobs into Windmill: Five Lessons from a Migration" /&gt;45 scheduled tasks. 25 were lying in crontab, 18 were hanging on user-level systemd timers, and 2 were pilot/split-tier tasks on the original cron. At 05:40 on August 24, 2026, I migrated them all into my self-hosted Windmill—45/45 smoke tests green, all original schedules removed.
If I&amp;rsquo;d done this sooner, I would&amp;rsquo;ve saved a lot of midnight log-diving. But the closer I got to actually doing it, the more I realized the migration itself had more pitfalls than cron ever did.</description></item><item><title>Installing a Control Plane for 'Script + Cron + Agent' Black-Box Automation: A Survey of 12 Platforms</title><link>https://blog.lynxflow.co/en/posts/2026-08-23-workflow-control-plane-selection/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/2026-08-23-workflow-control-plane-selection/</guid><description>&lt;img src="https://blog.lynxflow.co/images/2026-08-23-control-plane-architecture-cover.png" alt="Featured image of post Installing a Control Plane for 'Script + Cron + Agent' Black-Box Automation: A Survey of 12 Platforms" /&gt; TL;DR: What I need isn&amp;rsquo;t another orchestration tool, but a Control Plane—a coordination layer that answers in one place: which workflow, which version, which run, which step failed, how many retries, when&amp;rsquo;s the next run. cron only knows how to &amp;ldquo;knock on time&amp;rdquo; and then walks away. After surveying 11 platforms, my pick: Windmill first choice, Kestra co-selected; n8n/Temporal/Argo explicitly rejected; Hermes demoted to &amp;ldquo;scheduled agent&amp;rdquo; instead of scheduler.</description></item></channel></rss>