Fabric connects Kubernetes clusters with WireGuard
Fabric connects your Kubernetes clusters with WireGuard. Learn how an eBPF firewall, VPN access, and Loopback RBAC bring your network management together.
Fabric connects your Kubernetes clusters with WireGuard. Learn how an eBPF firewall, VPN access, and Loopback RBAC bring your network management together.
Kubernetes clusters need a network that lets their hosts communicate and remain accessible for administrative tasks. With multiple clusters across different infrastructure locations, this network layer becomes a distinct part of your architecture.
Fabric is Loopback's network layer. WireGuard connects Kubernetes clusters through encrypted links, an eBPF firewall filters traffic on the nodes, and a VPN provides administrative access. Management uses the same organization and access controls as the rest of your stack.
Running clusters requires answers to several questions: how is data transferred between hosts? Which traffic may reach a node? And how does your team access the infrastructure?
These tasks are related but serve different purposes:
| Task | Technical component in Fabric |
|---|---|
| Encrypted communication between cluster hosts | WireGuard |
| Filtering network traffic on the nodes | eBPF firewall |
| Administrative access to the nodes | VPN |
| Permissions for network management | Loopback RBAC |
This distinction also helps with planning. Encryption protects data in transit. Firewall rules control permitted traffic. Administrative access defines how your team reaches the hosts.
Fabric brings these components together in the platform.
WireGuard is a VPN protocol that transports encrypted IP packets over UDP. The communicating endpoints are called peers and identify themselves using cryptographic keys. A WireGuard interface connects ordinary IP communication to the encrypted tunnel.
In simplified terms, transmission works as follows: a host sends an IP packet to the tunnel interface. WireGuard maps the destination to a peer, encrypts the packet, and sends it to that peer's endpoint. At the other end, the packet is authenticated, decrypted, and processed.
Fabric uses WireGuard for peer-to-peer connections between Kubernetes clusters. Traffic between cluster hosts is encrypted. The clusters' private network also uses this layer.
For your team, the connection becomes part of the platform: the network layer belongs to cluster operations and is managed alongside the infrastructure.
Alongside encrypted transmission, a cluster needs rules that define which traffic may reach its hosts.
Fabric uses an eBPF firewall on every Kubernetes node. Filtering takes place directly on the host receiving the network traffic.
eBPF allows programs to run at defined execution points in the operating system. These include network events. This makes it possible to implement packet processing and filtering functions in the kernel without changing its source code.
This approach places the decision about a packet within the host's network processing. Rules can determine which traffic is processed further and which is dropped.
In Fabric, this host-based firewall also provides DDoS protection on the data plane. It forms part of the protection on the Kubernetes nodes.
During operations, your team needs a defined route to the cluster hosts. This includes investigating a connection problem or checking whether a node is reachable.
Fabric provides VPN access to the Kubernetes nodes. Alongside communication between hosts, this gives your team a route for administration.
This distinction helps when designing your architecture: application reachability and administrative access to its host serve different purposes. An application exposes the intended interfaces to its users. VPN access serves the team operating the infrastructure.
When planning each access path, you can specify who needs to reach which destination and for what task.
Suppose your team operates two clusters at different infrastructure locations. The cluster hosts need encrypted communication, while the operations team also needs access to the nodes.
Fabric handles several tasks in this architecture:
The application architecture builds on this foundation. Your team defines, for example, which services should communicate across clusters and which endpoints must be reachable by users.
The shared network layer provides the connection and controls. Your application's requirements determine the intended communication paths.
Changes to a tunnel or firewall affect infrastructure reachability. Assigning permissions therefore belongs in your network planning.
Fabric uses Loopback RBAC for this purpose. Within your organization, you define who may view or change tunnels, the firewall, and VPN settings.
This supports a clear way of working: people receive the permissions they need for their tasks. Those maintaining applications may need different permissions from those responsible for network configuration.
Network management follows the same organizational model as the other products on Loopback.
With Fabric, you manage the connections between your clusters, host protection, and administrative access within the same platform.
WireGuard handles encrypted transmission. The eBPF firewall filters traffic directly on the nodes. Your team reaches the hosts through the VPN, while Loopback RBAC controls management permissions.
Networking becomes an integrated part of your Kubernetes operations. Clusters, network functions, and access permissions remain within a shared management context.
Start with managed Kubernetes, object storage, registry, or Bundles. One account, one permission model.