<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Discovery on Open Component Model</title><link>https://ocm.software/tags/discovery/</link><description>Recent content in Discovery on Open Component Model</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 30 Jul 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://ocm.software/tags/discovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Component Discovery - the Missing Kubernetes Primitive</title><link>https://ocm.software/blog/designing-a-discovery-api/</link><pubDate>Thu, 30 Jul 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/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></channel></rss>