<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Cozystack</title><link>https://cozystack.io/article_types/networking/</link><description>Recent content in Networking on Cozystack</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Jul 2026 13:24:53 +0500</lastBuildDate><atom:link href="https://cozystack.io/article_types/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Network Isolation Between Tenants on Bare Metal: Cilium eBPF Policies, Plus Kube-OVN VPC</title><link>https://cozystack.io/blog/2026/07/network-isolation-between-tenants-cilium-ebpf-kube-ovn-vpc/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://cozystack.io/blog/2026/07/network-isolation-between-tenants-cilium-ebpf-kube-ovn-vpc/</guid><description>&lt;p&gt;Multi-tenant infrastructure without network isolation is a ticking time bomb. One misconfigured service in Tenant A can scan, attack, or accidentally connect to Tenant B&amp;rsquo;s databases. In AWS you get this by default — VPCs and security groups. On bare metal? You&amp;rsquo;re usually left stitching together CNI policies, overlays, and hoping nobody makes a mistake.&lt;/p&gt;
&lt;p&gt;Cozystack solves this out of the box with two complementary layers: &lt;strong&gt;tenant isolation enforced by Cilium eBPF&lt;/strong&gt; (always on, zero config), and &lt;strong&gt;optional Kube-OVN VPCs&lt;/strong&gt; for workloads that need their own dedicated subnets.&lt;/p&gt;</description></item></channel></rss>