Architecture

Mon, 01 Jan 0001 00:00:00 +0000

Overview

The gNMIc Operator follows the Kubernetes operator pattern to manage gNMIc telemetry collectors. It watches Custom Resources and reconciles the actual state with the desired state.

Components

This diagram illustrates how the gNMIc Operator orchestrates gNMIc deployments inside a Kubernetes cluster by reconciling Custom Resources into concrete Kubernetes primitives and gNMIc configurations.

At the core, the Cluster Controller watches a set of CRDs. It uses their desired state to create and manage resources like ConfigMaps, Secrets, Services, and a StatefulSet. The StatefulSet, together with the associated Services, materializes as multiple gNMIc pods (e.. gnmic-0, gnmic-1, gnmic-2), each responsible for a subset of targets.

Resource Model

Mon, 01 Jan 0001 00:00:00 +0000

Overview

The gNMIc Operator uses a set of Custom Resource Definitions (CRDs) to model telemetry infrastructure. The resources are designed to be composable and reusable.

Resource Hierarchy

Separation of Concerns

Each resource type handles a single concern:

Resource	Concern	Lifecycle
Cluster	Infrastructure	Where and how to run collectors
Pipeline	Wiring	What connects to what
Target	Device	Network device to collect from
TargetSource	Discovery	Dynamic target discovery
TargetProfile	Credentials	How to authenticate
TunnelTargetPolicy	Tunnel Matching	Rules for tunnel-connected devices
Subscription	Data	What paths to subscribe to
Output	Destination	Where to send data
Input	Source	External data sources
Processor	Transformation	How to transform data

Resource Selection

Resources are tied together in two main ways:

Concepts on gNMIc Operator

Architecture

Overview

Components

Resource Model

Overview

Resource Hierarchy

Separation of Concerns

Resource Selection