Cello CNI
5.8#12 in container networking softwareFree planFree planLinuxSelf-hosted
VisitCello CNI vs kube-network-policies
kube-network-policies
6.2#4 in container networking softwareFree planFree planLinuxSelf-hosted
VisitWhat both publish
| Fact | Cello CNI | kube-network-policies |
|---|---|---|
| Installation | The README instructs users to configure Cello and install it with Helm 3.0 or later. | The quick start documents installation using raw Kubernetes manifests or Helm in the kube-system namespace. |
| License | Cello is distributed under the Apache 2.0 license. | The repository lists the Apache-2.0 license. |
| Purpose | Cello is a Kubernetes CNI plugin based on the Volcengine VPC network that lets cluster workloads communicate within the VPC. | A userspace implementation that enforces Kubernetes network policies by intercepting packets with Linux NFQUEUE. |
| Security reporting | The security policy asks reporters to contact ByteDance's security team or [email protected] and not file public GitHub issues for vulnerabilities. | The project directs users to the Kubernetes Security and Disclosure Information page to report vulnerabilities. |
| Support | The project directs questions and contributions to GitHub issues or pull requests and also mentions maintainer email and a Feishu group. | The repository README lists the Kubernetes Slack #sig-network channel and the sig-network mailing list for maintainers and community support. |
Cello CNI plans
- Cello CNIFree
kube-network-policies plans
- Open-source projectFree
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 kube-network-policies if…
This project suits Kubernetes operators who need policy evaluation for Linux environments and can work with Kubernetes manifests or Helm. Its KIND-based development setup is relevant to developers with Docker, KIND, and kubectl.