opentelemetry.io OpenTelemetryCollector
and Instrumentation. Native list columns add reconciliation/configuration status
while retaining mode, version, image, management and instrumentation settings.
Collector details show deployment mode, management state, the reported Pod-count
snapshot, version/image and configured pipelines. Each pipeline lists receiver,
processor and exporter component names; components declared as connectors are
marked explicitly. Five pipelines are shown initially, with a control to show all.
Collector v1beta1 structured configuration and served v1alpha1 YAML configuration
are supported. An unreadable preview directs you to YAML rather than claiming the
configuration has no pipelines.
Reconciliation is separate from runtime health. The operator writes Ready=True
when reconciliation succeeds, even if collector Pods are unready. Radar labels
this Reconciled, with a neutral status. Earlier-generation observations are
Status stale. Inspect the generated Deployment, DaemonSet or StatefulSet through
existing ownership/Related Resources for current workload readiness. Reported Pod
counts are a reconciliation-time snapshot: ready/observed total for Deployment
and StatefulSet, or ready/desired scheduled Pods for DaemonSet.
Neither readiness nor configuration proves telemetry delivery.
Instrumentation details show the declared OTLP endpoint, propagators, sampler and
runtime images. The configuration is Configured, not healthy; blocked automatic
image upgrades are highlighted. This does not attribute injected Pods or infer
collector relationships from endpoint strings.
REST and MCP: existing resource list/get tools gain concise native summaries.
Collector summaries include reconciliation state, mode, version and image.
The optional openTelemetryCollector.reportedPodReadiness is the operator’s Pod-count snapshot,
not current readiness; read failures or a switch to sidecar mode can retain an
earlier value. openTelemetryCollector.declaredPipelines gives the declared count and
up to five sorted names, with truncation reported. That block is omitted when
configuration cannot be previewed; omission does not mean zero pipelines. Alpha
YAML previews are limited to 64 KiB. Instrumentation summaries name up to ten
languages under openTelemetryInstrumentation.recordedUpgradeBlocks, using the
same {count,names,namesTruncated} preview as declared pipelines,
without copying arbitrary status messages. These are additive summary fields;
no new MCP tool is introduced. Existing generic ownership remains;
no endpoint-derived topology edges, telemetry queries, or new Issues source are added.
Existing condition Issues surface managed reconciliation failures and status-read
errors with the operator’s message; unmanaged and stale observations are suppressed.
A status-read warning does not establish a Collector Pod failure.
Permissions: the Helm chart already collects
opentelemetry.io resources when
rbac.crdGroups.opentelemetry is enabled. The Cloud integration-read baseline does
not grant these full objects to default caller tiers: collector configuration and
instrumentation environment values can contain credentials. Supply explicit
customer-managed read permissions for caller-authorized tools when needed. This
baseline exception is not a full-object UI/REST confidentiality guarantee; runtime
response authorization remains separate. It does not revoke
permissions already granted by other roles.
Instrumentation upgrade history
The neutral “Upgrade block recorded” status describesstatus.upgradeBlockedVersions, written during an operator startup upgrade pass. A record can remain after a manual image change; it is not a current compatibility or runtime-health verdict. The drawer shows at most ten recorded languages, with shortened labels and a link to full YAML for remaining entries. Compact agent summaries retain their bounded language preview; detail reads retain native status without a duplicate context block.