Milestone summary: GoEPC Milestone 1: Build a K8s-based GoEPC user plane using a segmented+routed network #329
Description
Summary of https://github.com/cncf/cnf-testbed/milestone/56
Value:
- Meetings customer requirements (network security policies)
- Cloud native principles: declarative apis and config, observability
- K8s-native
Initial Goal: Send traffic through separated isolated and routed networks in the EPC user plane
Requirements:
- Must support using separate routed networks (eg. usually multiple interfaces) for EPC services
- Must support 3GPP standards for S-GW and P-GW including GTP tunnels
- Must use declarative K8s native configuration
- Minimize out-band, non-K8s, no custom vendor stuff if possible
- Should re-use existing EPC software for the services (eg. OpenAirInterface, OMEC, go-gtp) rather than writing them from scratch
- Go-gtp chosen
- Must run on Kubernetes
Phases:
- POC go-gtp, host-only version running on Packet Create a Go-GTP host-only EPC user plane example with a pseudo eNB and MME for testing #323 and Test and document the host-only Go-GTP EPC user plane on Packet #312
- POC Docker version running on Packet POC deployment of the GoGTP EPC user-plane using Docker #328 and Create a minimal docker version of the GoEPC with local Docker network connections #324
- POC single-node bridged network version running on K8s with Helm charts for CNFs Create a single-node bridged network version of the GoEPC use case using Multus #327
- - POC multi-node bridged network version Create a multi-node bridged network version of the GoEPC use case #330
- - POC routed network version NEEDS PLANNING => Create a single/multi-node routed network version of the GoEPC use case using Multus #331
Diagram:
