projectcalico / vpp-dataplane

VPP dataplane implementation for Calico
Apache License 2.0
148 stars 38 forks source link

Calico VPP dataplane

This repository contains the source for Calico's VPP dataplane integration. The integration is in incubation status, with significant development in progress.

Integration goals

The main goal of this integration is to accelerate the networking of k8s clusters that use Calico thanks to FD.io VPP. Nodes running the VPP dataplane provide faster networking to their pods, without requiring any changes to the applications running in the pods.

This integration aims to be as transparent as possible. In particular, the VPP dataplane does not have any additional requirements compared to regular Calico. All the networking configuration, including traffic encapsulation, IP Pools, BGP Configuration, etc. is done through regular Calico means. As a result, the docs present in this repository will only describe the VPP-specific elements.

VPP-enabled nodes are entirely compatible with regular Calico nodes - meaning that it is possible to have a cluster with some VPP-enabled nodes and some regular nodes. This makes it easy to migrate a cluster from Linux or eBPF Calico networking to VPP-accelerated networking.

In addition to that, the VPP Dataplane provides some additional features that are not available in Calico. For instance :

Finally, our goal is to make the deployment of Calico-VPP as simple as applying a YAML file through kubectl.

Get Started Using Calico/VPP

Software Architecture

For technical details about the Calico-VPP integration, see the VPP dataplane implementation details.

Contributing

Contributions to this code are welcome!

Before starting, make sure you've read the Calico contributor guide.

You can follow the guide to setup a kind based development cluster

Or refer to the developer documentation in this repository

License

Calico binaries are licensed under the Apache v2.0 license, with the exception of some GPL licensed eBPF programs.

Calico imports packages with a number of apache-compatible licenses. For more information, see licenses. In addition, the base container image contains pre-packaged software with a variety of licenses.