Kube-VIM
NFV, the Kubernetes way
An ETSI NFV-MANO compliant Virtual Infrastructure Manager that runs virtual network functions on Kubernetes, next to your cloud-native workloads.
Open source · Apache 2.0 · backed by Retelith
Carrier NFV, without a parallel stack
Standards-compliant on the outside, plain Kubernetes on the inside.
KRM-native
Every managed resource is a Kubernetes object in etcd. Kube-VIM reconciles NFV resources like a native controller, with no external database and no drift.
ETSI VIM, any NFVO
Or-Vi and Vi-Vnfm over gRPC and REST, with a generated OpenAPI client. Validated with OSM through an OSM connector.
Line-rate data plane
SR-IOV with hardware offload for near-line-rate throughput. Overlay, underlay, and SR-IOV networks today; vDPA and vhost-user planned.
Converged NFV
Run VNFs alongside your CNFs on the same hardware and the same network fabric. Convergence comes from being Kubernetes-native.
Hyperconverged and portable
Runs on any Kubernetes distribution. Proven on Talos Linux in a hyperconverged edge topology.
Easy to deploy
A single Helm bundle ships Kube-VIM together with the components it drives. GitOps-friendly and simple to stand up.
Built on trusted OSS
Stands on KubeVirt, CDI, Kube-OVN, and Multus, with no vendor, NIC, or distribution lock-in.
Observable
Prometheus metrics out of the box, with correlation labels that tie backend series to ETSI resource IDs.
A thin control plane for NFV on Kubernetes
It sits between your NFV orchestrator and your cluster, and gets out of the way.
Standards-first
Kube-VIM speaks the ETSI reference points, Or-Vi and Vi-Vnfm, over both gRPC and REST with an OpenAPI client. Any ETSI-compatible NFV orchestrator can drive it, so you are not tied to a single MANO stack.
Kubernetes-native
It turns orchestrator requests into Kubernetes Custom Resources and manages their lifecycle, statelessly. There is no separate datastore. Every managed resource lives as a Kubernetes object in etcd.
Truly converged
Because it reuses standard components like KubeVirt, Kube-OVN, and Multus, your VNFs share the same network and the same resource pool as your CNFs. One cluster, one fabric, no parallel infrastructure.
Open source, built by telco people
Kube-VIM is open source under Apache 2.0, backed and supported by Retelith, a telecom software company building Kubernetes-native infrastructure for network operators.
Star on GitHub