<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Open Component Model</title><link>https://ocm.software/0.14/blog/</link><description>Recent content in Blog on Open Component Model</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 03 Aug 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://ocm.software/0.14/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>We did a Hackathon!</title><link>https://ocm.software/0.14/blog/2026-08-03-ipcei-cis-hackathon-potsdam/</link><pubDate>Mon, 03 Aug 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/2026-08-03-ipcei-cis-hackathon-potsdam/</guid><description>&lt;h2 id="hackathon--sap-innovation-center-potsdam"&gt;Hackathon @ SAP Innovation Center Potsdam&lt;/h2&gt;
&lt;p&gt;From 21.07.2026 to 24.07.2026 we attended an SAP Hackathon @ &lt;a href="https://maps.app.goo.gl/xWjXeojfLuXJdyzw8" target="_blank" rel="noopener"&gt;SAP Innovation Center in Potsdam&lt;/a&gt;. This is
one of, if not the best, locations that SAP has around the globe. SAP was so nice to provide us with food, drinks and a
lovely set of people to work together with on interesting projects in the IPCEI-CIS initiative.&lt;/p&gt;</description></item><item><title>Component Discovery - the Missing Kubernetes Primitive</title><link>https://ocm.software/0.14/blog/designing-a-discovery-api/</link><pubDate>Thu, 30 Jul 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/designing-a-discovery-api/</guid><description>&lt;h2 id="the-manual-grind"&gt;The Manual Grind&lt;/h2&gt;
&lt;p&gt;Platforms like &lt;a href="https://github.com/openmcp-project" target="_blank" rel="noopener"&gt;OpenControlPlane&lt;/a&gt; run service providers that install and manage services (Flux, Crossplane, Kro, &amp;hellip;) on behalf of their users. Each service provider needs to know which versions of a service are available and where to fetch the corresponding artifacts from. Today, that means hardcoding OCI references (image URLs, chart registries, pull secrets) into provider configs, per version, per service:&lt;/p&gt;</description></item><item><title>Creating an OCM Component for a non-trivial Application</title><link>https://ocm.software/0.14/blog/2026-07-30-ocmifying-thalamus/</link><pubDate>Thu, 30 Jul 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/2026-07-30-ocmifying-thalamus/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://cobaltcore-dev.github.io/thalamus/main/" target="_blank" rel="noopener"&gt;Thalamus&lt;/a&gt; is a large project with many moving parts. At the time of
this writing, it has 11 components that must be bundled together so the entire stack can be deployed as one.&lt;/p&gt;</description></item><item><title>Shipping SBOMs with Your Components</title><link>https://ocm.software/0.14/blog/2026-07-28-shipping-sboms-with-your-components/</link><pubDate>Tue, 28 Jul 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/2026-07-28-shipping-sboms-with-your-components/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;OCM already tells you &lt;em&gt;which artifacts&lt;/em&gt; a component delivers: its Software Bill of Delivery. But that does not answer the question a security team actually has: &lt;em&gt;&amp;ldquo;which dependencies are bundled inside those artifacts, and am I affected by this vulnerability?&amp;rdquo;&lt;/em&gt; Knowing a component ships an OCI image and a CLI binary as a resource does not tell anything about the packages and libraries buried inside that resource.&lt;/p&gt;</description></item><item><title>Welcome Ilja Weis to the OCM Technical Steering Committee</title><link>https://ocm.software/0.14/blog/2026-07-23-welcome-ilja-weis-tsc/</link><pubDate>Thu, 23 Jul 2026 12:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/2026-07-23-welcome-ilja-weis-tsc/</guid><description>&lt;p&gt;We are glad to announce that &lt;a href="https://github.com/iljaweis" target="_blank" rel="noopener"&gt;Ilja Weis&lt;/a&gt; from
&lt;a href="https://www.bwi.de/" target="_blank" rel="noopener"&gt;BWI GmbH&lt;/a&gt; has been voted into the OCM Technical Steering Committee.&lt;/p&gt;
&lt;p&gt;BWI, the IT service provider for the German Armed Forces,
&lt;a href="https://neonephos.org/blog/20260218_bwi_joins_neonephos" target="_blank" rel="noopener"&gt;joined the NeoNephos Foundation as a Premier Member&lt;/a&gt;
earlier this year. Since then, the collaboration has been active: BWI contributed
&lt;a href="https://github.com/open-component-model/community" target="_blank" rel="noopener"&gt;ocm-kit&lt;/a&gt; to the OCM community repository, a Go library and CLI tool
for working with OCM-based Helm values templates. The TSC
&lt;a href="https://github.com/open-component-model/open-component-model/blob/main/docs/steering/meeting-notes/2026-04-07.md" target="_blank" rel="noopener"&gt;accepted the contribution unanimously&lt;/a&gt;
in April 2026.&lt;/p&gt;</description></item><item><title>OCM v2: A Fresh Foundation for Secure Software Delivery</title><link>https://ocm.software/0.14/blog/ocmv2/</link><pubDate>Mon, 30 Mar 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/0.14/blog/ocmv2/</guid><description>&lt;p&gt;We are excited to announce &lt;strong&gt;OCM v2&lt;/strong&gt; — a ground-up rebuild of the Open Component Model tooling stack. A new CLI, Kubernetes controllers, and Go library — designed from the start for modularity, security, and community contribution. The entire stack continues to implement the &lt;a href="https://github.com/open-component-model/ocm-spec/blob/main/doc/04-extensions/00-component-descriptor/v2.md" target="_blank" rel="noopener"&gt;OCM Specification v2&lt;/a&gt;, ensuring full compatibility with the standard that defines how components, resources, and signatures are represented.&lt;/p&gt;</description></item><item><title>What changed between legacy and new OCM Controllers</title><link>https://ocm.software/0.14/blog/2026-03-16-ocm-controllers-differences/</link><pubDate>Mon, 16 Mar 2026 10:00:00 +0100</pubDate><guid>https://ocm.software/0.14/blog/2026-03-16-ocm-controllers-differences/</guid><description>A walkthrough of the major architectural changes between the legacy ocm-controller and the new ground-up rebuild.</description></item></channel></rss>