Page History

Type

New

Blueprint Family - Proposed Name

Kubernetes-Native Infrastructure for Edge (KNI-Edge) 

Use Case(s)

various, e.g.:

• Provider Access Edge (Far/Near), MEC

• Industrial Automation

• Enterprise Edge

• ...

Blueprint Proposed

various; initially:

• Provider Access Edge (PAE)

• Industrial Edge (IE)

Initial POD Cost (CAPEX)

(depends on blueprint) 

Scale

1 to hundreds of nodes, 1 to thousands of sites.

Applications

any type of workloads:

• containerized or VM-based

• real-time, ultra-low latency or high-throughput

• NFV, IoT, AI/ML, Serverless, ...

Power Restrictions

(depends on blueprint)

Preferred Infrastructure Orchestration

End-to-end Service Orchestration: depends on use csae; e.g. ONAP
App Lifecycle Management: Kubernetes Operators
Cluster Lifecycle Management: Kubernetes Cluster API/Controller
Container Platform: Kubernetes (OKD)
Container Runtime: CRI-O w/compatible backends
VM Runtime: KubeVirt
OS: CentOS, CentOS-rt, or CoreOS 

Additional Details