<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VLAN on Sebastian Scheinkman - Red Hat Openshift, Networking, Kubernetes and Cloud Native</title><link>https://sebasblog.com/tags/vlan/</link><description>Recent content in VLAN on Sebastian Scheinkman - Red Hat Openshift, Networking, Kubernetes and Cloud Native</description><generator>Hugo</generator><language>en-us</language><copyright>sebasblog.com</copyright><atom:link href="https://sebasblog.com/tags/vlan/index.xml" rel="self" type="application/rss+xml"/><item><title>DRA Chainable Networking Proposal</title><link>https://sebasblog.com/docs/dra-chainable-networking-proposal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sebasblog.com/docs/dra-chainable-networking-proposal/</guid><description>&lt;h1 id="dra-chainable-networking"&gt;DRA Chainable Networking&lt;/h1&gt;
&lt;p&gt;A proposal for declarative, composable network configuration in Kubernetes
using DRA device requests with &lt;code&gt;dependOn&lt;/code&gt; chaining — enabling bonding, VLANs,
tuning, and mixed NIC + GPU topologies in a single &lt;code&gt;ResourceClaim&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Constraint: this proposal uses only the existing DRA API (DeviceClass,
ResourceClaim, ResourceSlice, opaque config). No upstream API extensions are
required.&lt;/strong&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-problem-statement"&gt;1. Problem Statement&lt;/h2&gt;
&lt;p&gt;Today&amp;rsquo;s DRA network drivers face a fundamental limitation: &lt;strong&gt;complex network
topologies cannot be expressed declaratively within the DRA API&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>