Cello CNI
5.8#12 in container networking softwareFree planFree planLinuxSelf-hosted
VisitCello CNI vs Network Service Mesh
Network Service Mesh
7.0#2 in container networking softwareFree planFree planAPILinuxSelf-hosted
VisitWhat both publish
| Fact | Cello CNI | Network Service Mesh |
|---|---|---|
| Deployment requirements | The README specifies Volcengine ECS with kernel 4.19 or later, notes testing on veLinux 1.0 with kernel 5.10, and recommends kubeadm for Kubernetes installation. | The run guide lists Docker, Go, a Kubernetes cluster, and kubectl as prerequisites; it says most examples require at least two worker nodes. |
| License | Cello is distributed under the Apache 2.0 license. | The public Network Service Mesh GitHub repositories shown are licensed Apache-2.0. |
| Purpose | Cello is a Kubernetes CNI plugin based on the Volcengine VPC network that lets cluster workloads communicate within the VPC. | Network Service Mesh is a hybrid and multi-cloud IP service mesh for connecting workloads across clusters and clouds. |
Cello CNI plans
- Cello CNIFree
Network Service Mesh plans
- Network Service MeshFree
Pick Cello CNI if…
Cello CNI suits teams running Kubernetes workloads on Volcengine ECS that need Pod networking within a VPC. It is intended for environments able to meet its kernel, Helm, and cloud IAM requirements.
Pick Network Service Mesh if…
It suits teams connecting Kubernetes pods, virtual machines, or physical servers across clusters and clouds. It is relevant to operators who want per-workload Network Services and can meet the listed deployment prerequisites.