https://sebasblog.com/tags/telco/Recent content in Telco on Sebastian Scheinkman - Red Hat Openshift, Networking, Kubernetes and Cloud NativeHugoen-ussebasblog.comhttps://sebasblog.com/docs/dra-chainable-networking-proposal/Mon, 01 Jan 0001 00:00:00 +0000https://sebasblog.com/docs/dra-chainable-networking-proposal/<h1 id="dra-composable-networking-with-grpc-networkplugins">DRA Composable Networking with gRPC NetworkPlugins</h1> <blockquote> <p><strong>Status:</strong> Proposed architecture for review; not an implemented or upstream Kubernetes API.<br> <strong>Revision:</strong> 2026-09-16 — typed-reference, IPAM/MAC, workload-context, and stable-identity extension of the four-hook design.<br> <strong>Companions:</strong> <a href="dra-network-device-discovery-design.md">Network Device Discovery and ResourceSlice Design</a> and <a href="dra-network-framework-plugin-sdk.md">Framework and Plugin SDK</a>.<br> <strong>Terminology:</strong> NetworkPlugins are the small execution components defined here. Existing CNI implementations may supply reusable code, but their binary protocol, configuration schemas, and result semantics are not this protocol.<br> <strong>Reading the examples:</strong> Kubernetes <code>resource.k8s.io/v1</code> objects use upstream APIs. <code>networking.dra.io/*</code> resources, plugin schemas, protocol messages, labels, and state machines are project proposals. They require implementation and installation before use. Example driver/API domains retain the original draft&rsquo;s spelling; the project must select domains it controls before release.</p>