How omec-project/sdcore-helm-charts works
Project type and purpose
• This repo is a collection of Helm charts (Kubernetes package manager) designed to deploy Aether SD-Core on a K8s cluster.
• It includes an umbrella chart (sdcore-helm-charts) that pulls in several sub-charts:
– 5G Control Plane (5g-control-plane / omec-control-plane)
– RAN Simulator (5g-ran-sim)
– Subscriber Provisioner (omec-sub-provision)
– User Plane (BESS-UPF) (bess-upf)
– Router service (router)
– Test applications (5g-test-apps)
File structure
• Top-level directories are individual Helm charts, each with:
• Chart.yaml, values.yaml, templates/ (configmap, deployment, service, statefulset, scripts)
• The umbrella chart (sdcore-helm-charts) declares dependencies on those sub-charts.
• Each sub-chart follows the standard Helm pattern: templated ConfigMaps, Secrets, Deployment/StatefulSet, Service, plus bin/*.tpl startup scripts.
• CI/CD workflows (.github/workflows) automate linting, packaging, and pushing charts.
Insights from the README
• Emphasizes overriding values.yaml with Aether-OnRamp’s sdcore-5g-values.yaml for real deployments.
• The charts deploy all network functions required by 5G core (AMF, SMF, PCF, UDM, NRF, NSSF, etc.), plus user-plane and RAN simulator.
• OnRamp handles cluster networking for N2/N3/N6 interfaces; charts expect those to be configured.
– Clear labels: “Umbrella Chart”, “Control Plane Chart”, “RAN Sim Chart”, etc.
• Control-plane signaling (N2, N11, Nrf API calls)
• Data-plane flow (N3, N6)
• Provisioning calls (simapp → webui API)
• Blue for control-plane functions
• Green for data-plane (UPF)
• Orange for simulator/test apps
• Gray for Helm/templating layer
• Hexagons for external systems