Skip to main content
Because Chronosphere Telemetry Pipeline is a collection of Kubernetes resources, Telemetry Pipeline uses the Kubernetes labeling system to categorize and identify these resources. You can’t change these labels yourself, but Telemetry Pipeline applies labels consistently across resources, which means you can use them to select specific resources while performing Kubernetes operations.

​
Label format and types

Telemetry Pipeline resource labels use a key/value pair format separated by an equal sign (key=value). All resource of the same type receive the same set of keys, but certain keys’ values contain information unique to a particular instance of a resource, like a name or UUID.

​
List of resource labels

Each resource in Telemetry Pipeline receives the following labels:
Resource typeLabels
Core Operator podcalyptia.core=core-operator
control-plane=controller-manager
Core Operator metrics servicecalyptia.core=core-operator
control-plane=controller-manager
Core Instance podapp.kubernetes.io/part-of=calyptia
Core Instance metrics servicenone
Pipeline podapp.kubernetes.io/component=calyptia-core
core-pipeline=[PIPELINE NAME]
Cluster logging pipeline podapp.kubernetes.io/component=calyptia-core
core-pipeline=[INSTANCE NAME]-cluster-logging-[UUID]
Pipeline serviceapp.kubernetes.io/created-by=core-operator
app.kubernetes.io/managed-by=core-operator
app.kubernetes.io/part-of=calyptia
calyptia.core=core-operator
Health check podapp.kubernetes.io/component=calyptia-core
core-pipeline=[INSTANCE NAME]-health-check-[UUID]
Health check servicecalyptia.core=core-operator