This section provides users with Container4NFV gap analysis regarding feature requirement with Kubernetes Official Release. The following table lists the use cases / feature requirements of container integrated functionality, and its gap analysis with Kubernetes Official Release.
| Use Case / Requirement | Supported in v1.5 | Notes |
|---|---|---|
| Manage conainter and virtual machine in the same platform. | No | There are some ways how Kubernetes could manage VM-s:
|
| Kubernetes support multiple networks. | No | As VNF needs at least three interfaces. Management,control plane, data plane. CNI already supports multiple interfaces in the API definition. |
| Kubernetes support NAT-less connections to a container | No | SIP/SDP and SCTP are not working with NAT-ed networks |
| Kubernetes scheduling support CPU binding，NUMA features | No | The kubernetes schedular don’t support these features |
| DPDK need to support CNI | No | DPDK is the technology to accelerate the data plane. Container need support it, the same with virtual machine. |
| SR-IOV can support CNI (Optional) | No | SR-IOV could let container get high performance |