<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Standards on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/standards/</link><description>Recent content in Standards on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:07:53 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/standards/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Workload Conformance Working Group announced</title><link>https://curadevops.metacog.co.kr/insights/2026-10-27-announcing-the-workload-conformance-working-group/</link><pubDate>Tue, 27 Oct 2026 16:07:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-27-announcing-the-workload-conformance-working-group/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> The WG targets exactly the repeated per-cluster workload assessments operators do today — node-drain tolerance, removed-API dependencies, over-privileged containers. Worth tracking as the spec develops, but the deliverable doesn&amp;rsquo;t exist yet so there&amp;rsquo;s nothing to act on.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A Kubernetes-blessed workload conformance standard could eventually reduce per-environment onboarding overhead and inform the org&amp;rsquo;s golden-path requirements, but the working group is newly chartered with no published spec yet — no planning decision warranted now.&lt;/li>
&lt;/ul></description></item></channel></rss>