cncf / cncf/telecom-user-group
1.5.4 Evolving the Stack From VNFs to CNFs include CNV's (container native virtualization)
- Dominant language
- No language data
- Stars
- 129
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
The emergence of Kubernetes as the most widely used container orchestration layer allows telecommunications operators to shift their infrastructure over from more bespoke, expensive, and higher friction stacks to a de facto standard platform while also improving performance and resiliency. The extensibility of Kubernetes should allow a gradual transition from legacy VNFs built on OpenStack or VMWare over to a Kubernetes telco stack that accommodates all aspects of their business - including legacy VNFs, which can be easily managed via an abstraction layer on top of Kubernetes (KubeVirt/CNV/Virtlet/Openstack).
Contributor guide
Research direction
Start by locating the document section titled “1.5.4 Evolving the Stack From VNFs to CNFs.” Review the existing discussion of Kubernetes, VNFs, CNFs, and virtualization abstractions, then update the section to address container-native virtualization and its relationship to the listed legacy-stack options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100