<?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/b1cf1db3300946b9b8fe48ae85bbfc26&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b1cf1db3300946b9b8fe48ae85bbfc26-00001.gif</thumbnail_url><duration>512.3333333333348</duration><title>Kubernetes Traffic Shifting Feature</title><description>Hey team, I&apos;m excited to announce the new Kubernetes feature we&apos;re launching. It&apos;s about traffic shifting during deployments, allowing safe routing of live traffic to new primary or canary instances. We&apos;ve integrated with popular ServiceMesh tools and have a plugin for Istio. In the product, we introduced a new step for traffic routing configuration. I&apos;ll walk you through an execution scenario and show you how to perform traffic shifting. Watch the Loom linked below for more details.</description></oembed>