Documentation for version: v0.1.0

What is flotta

Edge Devices Management For k8s Workloads

Flotta adds a way to manage all your edge devices from a single point using Kubernetes CRD to handle all kinds of device configurations.

Each edge device can register, pull configuration using the Flotta Edge API and keep syncing the data using a secure MTLS protocol between the device and the Flotta Edge API.

It is also possible to schedule a container workload to run in the device using a Workload CRD. A container workload can be scheduled for an unlimited number of devices.

flowchart TB classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; subgraph "Kubernetes" direction TB EdgeDevice(EdgeDevice CRD) EdgeDeviceSet(EdgeDeviceSet CRD) EdgeWorkload(EdgeWorkload CRD) ing(Ingress) --> api(Flotta Edge API) op(Flotta Operator) op -.- EdgeDevice op -.- EdgeDeviceSet op -.- EdgeWorkload api -.- EdgeDevice api -.- EdgeDeviceSet api -.- EdgeWorkload end class ing,op,api,EdgeDevice,EdgeDeviceSet,EdgeWorkload k8s; class kube cluster; subgraph Device direction LR; Agent((Agent daemon)); Agent --> Podman --> Workloads; end Agent ---> Device ---> ing

Edge Devices Observability

Device agents takes care of running container workloads, but at the same time, it also takes care of the following actions in the workload to make edge-administration life easier.

  • Get metrics from workloads and push to a remote serve when the connectivity is up.
  • Get logs from workloads and push to a remote server when the connection is up.

Device Configuration

Device configuration is a hard part on edge, this is why Flotta trusts RPM-OSTree technology to run updates on the non containerized workloads.

Each device can be configured as a single EdgeDevice CR - where all observability, logs, heartbeats can be set - or can be defined on DeviceSets CR. This grouping CRD allows configuring multiple edgedevices from a single unit, making easier the edge-administration life.

Because all the process is based on Kubernetes CRD, it is compatible with your favourite GitOps tools, so deploy pipelines can be defined across all of your edge devices.

OS Lifecycle

@TODO TBC