<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f83c1358a1c9422c8677762e11d6075e&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f83c1358a1c9422c8677762e11d6075e-1700164019759.gif</thumbnail_url><duration>499.8000000000015</duration><title>Replicated SDK: Unlocking Functionality for All Customers</title><description>In this video, I, Alex Parker from Replicated, discuss the Replicated SDK and how we now recommend all customers to include it as part of their application. Regardless of the packaging or installation method, whether it&apos;s helm or COTS, the SDK can be deployed and benefit from it. I explain how to include the SDK as a dependency in a helm chart and how to install it as a standalone helm chart. I also demonstrate how a single release with the SDK can be installed in both COTS and Helm installations. Action requested: Consider including the SDK in your application for additional functionality.</description></oembed>