<?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/81f608f80ca1493dbed01584d82fb5b9&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/81f608f80ca1493dbed01584d82fb5b9-00001.gif</thumbnail_url><duration>202.233</duration><title>Enforcing the Replicated License at Runtime</title><description>In this video, I address the common question of how to enforce licenses from the replicated platform at runtime. I explain that while the platform offers tools for distribution time enforcement, it does not provide enforcement once something is running. To tackle this, I introduce the concept of an init container that checks the license and prevents the pod from starting if the license is invalid. I demonstrate this by running Slacker News and expiring the license, showing how the init container keeps the pod from running and generates a Kubernetes event. By describing the pod, users can easily understand why it&apos;s not running. I also highlight the benefits of this approach, such as not needing to write code for individual applications.</description></oembed>