<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Platform-Architecture on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/platform-architecture/</link><description>Recent content in Platform-Architecture on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 11:17:39 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/platform-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>CNCF: Cloud-native platform sovereignty via multi-plane architecture</title><link>https://curadevops.metacog.co.kr/insights/2026-08-19-cloud-native-platform-sovereignty-through-multi-plane-archit/</link><pubDate>Wed, 19 Aug 2026 11:17:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-19-cloud-native-platform-sovereignty-through-multi-plane-archit/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Conceptual framing of multi-plane sovereignty architecture that could inform future platform design decisions, but no actionable change required today and no concrete deadline or migration target.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Useful strategic context on sovereignty architecture patterns for leaders weighing data-residency or regulatory requirements, but no vendor decision or cost implication is triggered by this piece.&lt;/li>
&lt;/ul></description></item><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><item><title>Kubernetes Pod-per-agent vs shared runtime for AI agents (kagent)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-14-is-a-pod-the-right-deployment-unit-for-an-ai-agent/</link><pubDate>Tue, 14 Jul 2026 12:06:40 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-14-is-a-pod-the-right-deployment-unit-for-an-ai-agent/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Explores the architectural tradeoffs of running each AI agent in its own Pod/ServiceAccount versus a shared runtime on Kubernetes — useful context for platform engineers who may be asked to support AI agent workloads. No action required today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Offers mental-model framing for how AI agent workloads map onto Kubernetes primitives, which could inform a platform strategy for AI/ML infrastructure — but no vendor, licensing, or cost decision is at stake.&lt;/li>
&lt;/ul></description></item></channel></rss>