Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Cello CNI

github.com

  • Free plan
  • Linux
  • Self-hosted
7.0 Club score Visit github.com

What Cello CNI is

Cello CNI is a Kubernetes networking plugin that connects cluster workloads within a Volcengine VPC. It builds Pod networks with secondary ENIs and offers shared ENI and ENI multi-IP modes; both support Pod-to-Pod and Pod-to-Node communication. Cello integrates Cilium in place of kube-proxy and supports ClusterIP, NodePort and LoadBalancer services. Its Cilium components support NetworkPolicy through eBPF programs on a Pod's primary device. A Kubernetes device plugin reports available network resources so the scheduler can place Pods on nodes with capacity. Pod capacity depends on ECS instance type and ENI quotas, and exclusive ENI mode supports fewer Pods than shared ENI mode. Cello allows cluster-wide and node-specific configuration, with some settings changeable at runtime without restarting its Pods. It is free under Apache 2.0. Deployment requires Volcengine ECS, Kubernetes and Helm 3.0 or later; ECS needs kernel 4.19 or later, and the project recommends kubeadm for Kubernetes installation. Volcengine IAM permissions are also required for ECS and VPC operations.

Who it suits

Cello is for teams running Kubernetes on Volcengine ECS that need Pod networking within a VPC. It is most relevant to administrators comfortable with the stated ECS, Kubernetes, kernel and Helm requirements.

Good to know, and what to watch

  • Free and distributed under Apache 2.0.
  • Supports Pod-to-Pod and Pod-to-Node communication.
  • Includes ClusterIP, NodePort and LoadBalancer support.
  • NetworkPolicy support uses eBPF programs.
  • Some configuration changes do not require Pod restarts.
  • Requires Volcengine ECS, Kubernetes and Helm 3.0 or later.
  • ECS instances need kernel 4.19 or later.
  • Pod capacity depends on instance type and ENI quotas.
  • Exclusive ENI mode supports fewer Pods than shared ENI mode.

Cello CNI

Free

Free plan

The verdict

Cello provides VPC-based Pod networking with service and NetworkPolicy support, at no license cost. Check ECS capacity, ENI quotas and the required IAM permissions before planning deployment.

What the maker publishes

Cloud integration
Cello requires Volcengine IAM permissions to call ECS and VPC APIs for instance, ENI, IP address, and subnet operations. source
Communication
Both network modes support Pod-to-Pod and Pod-to-Node communication. source
Configuration
Cello supports cluster-wide and node-specific configuration, and selected settings can be changed at runtime without restarting Cello Pods. source
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. source
Installation
The README instructs users to configure Cello and install it with Helm 3.0 or later. source
License
Cello is distributed under the Apache 2.0 license. source
Network policy
The project says its Cilium components support NetworkPolicy and use eBPF programs on a Pod's primary device. source
Pod networking
Cello uses secondary ENIs to build Pod networks and supports shared ENI and ENI multi-IP modes. source
Purpose
Cello is a Kubernetes CNI plugin based on the Volcengine VPC network that lets cluster workloads communicate within the VPC. source
Resource limit
Pod capacity depends on the ECS instance type and ENI quotas; exclusive ENI mode supports fewer Pods than shared ENI mode. source
Scheduling
Cello reports available network resources through a Kubernetes device plugin so the scheduler can place Pods on nodes with resources. source
Security reporting
The security policy asks reporters to contact ByteDance's security team or [email protected] and not file public GitHub issues for vulnerabilities. source
Services
Cello integrates Cilium in place of kube-proxy and supports ClusterIP, NodePort, and LoadBalancer services. source
Support
The project directs questions and contributions to GitHub issues or pull requests and also mentions maintainer email and a Feishu group. source

Checked against the maker's pages on 7 Oct 2026.