Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 34 Next »

Contact: Frank Zdarsky

Overview

The KNI-Edge Family unites edge computing blueprints sharing the following characteristics:

  • Implement the Kubernetes community’s Cluster API, allowing users to declaratively configure and consistently deploy and lifecycle manage Kubernetes clusters no matter whether on-prem or on public cloud, on VMs or on bare metal, at the edge or at the core.

  • Leverage the community’s Operator Framework for automated and secure lifecycle management of applications in the edge computing stack. Operators allow applications to be lifecycle managed as Kubernetes resources, in event-driven manner, and fully RBAC-controlled. They may provide more than deployment and upgrade actions for an application, e.g. auto-reblancing/scaling, analytics, and usage metering, and may be created from Helm Charts, using Ansible or Go.

  • Optimize for Kubernetes-native container workloads, but allow mixing in VM-based workloads via KubeVirt as needed.

Family Template

Attributes

Description

Informational

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:


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



Blueprints in this Family

Points of contact

Documents

Proposal Presentation

Meetings

Minutes

  • No labels