{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/81f608f80ca1493dbed01584d82fb5b9\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/81f608f80ca1493dbed01584d82fb5b9-00001.gif","duration":202.233,"title":"Enforcing the Replicated License at Runtime","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's not running. I also highlight the benefits of this approach, such as not needing to write code for individual applications."}