<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/systemd/</link><description>Recent content in Systemd on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 12:15:50 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing Kubernetes with systemd: a practical case study</title><link>https://curadevops.metacog.co.kr/insights/2026-07-16-replacing-kubernetes-with-systemd-2024/</link><pubDate>Thu, 16 Jul 2026 12:15:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-16-replacing-kubernetes-with-systemd-2024/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> A practitioner case study on replacing Kubernetes with systemd for simpler workloads — useful context for evaluating when Kubernetes complexity isn&amp;rsquo;t justified, but no operational change required.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Relevant for strategy discussions about Kubernetes adoption scope; provides a concrete counterpoint when evaluating whether all workloads warrant the operational overhead of a cluster.&lt;/li>
&lt;/ul></description></item></channel></rss>