# Cluster, workload, and span in one view

Install one Helm chart. Kubelet, host, and kube-state metrics flow in over OTLP. The OpenTelemetry Operator injects pod identity into every span your apps emit, so a slow request lands you on the exact replica that served it.

## Cluster and application, one pipeline

### helm install — Helm chart, not a black box

maple-k8s-infra is a small Helm chart you can read end-to-end. Kubelet stats per pod, host metrics per node, kube-state metrics across the cluster. OTLP receivers on every node for your apps.

### k8s.pod.name — Pod and span, joined

Spans arrive carrying k8s.pod.name, k8s.node.name, and k8s.namespace.name. Drill from a slow trace straight to the pod and node that ran it.

### kube-state — Kube-state metrics

Deployments, StatefulSets, DaemonSets, replica counts, and pod phase, all scraped via the standard kube-state-metrics exporter.

### /infra/kubernetes — Workloads, pods, and nodes

Three first-class infrastructure views in the dashboard. Inspect a deployment, a single pod, or a single node, with the same filters you use everywhere else.

### OTel Operator — OpenTelemetry Operator

Pods get OTEL_EXPORTER_OTLP_ENDPOINT and pod/node identity injected at admission. Apps with an OTel SDK linked are instrumented without code changes.

### one endpoint — Multi-cluster ingest

One ingest endpoint per organization. Send from prod, staging, and a developer's kind cluster, and split them with cluster-name resource attributes.

## Related

- [Service Catalog & Map](https://maple.dev/features/service-catalog.md)
- [Metrics & Dashboards](https://maple.dev/features/metrics-dashboards.md)
- [Distributed Tracing](https://maple.dev/features/distributed-tracing.md)
- [Microservices Debugging](https://maple.dev/use-cases/microservices-debugging.md)