KafkaConnector resources in kafka.strimzi.io through Issues, including the API and MCP. A connector can remain RUNNING while an individual task is FAILED; Radar checks both. Explicit connector/task failures and NotReady=True produce one warning per connector, attributed to Strimzi’s operator snapshot. Task IDs are bounded; configurations, exception messages and stack traces are not included in the issue.
Radar’s collector needs Kubernetes read access to the connector CRs, with no Kafka credentials or additional settings. Connectors managed only through the Connect REST API are outside this coverage. Radar does not connect to Connect or Kafka directly. Radar Cloud’s default integration-read role does not add kafkaconnectors access because full connector objects can contain credentials. Radar’s resource views and curated findings follow its namespace-level read policy; withholding a full-object Kubernetes grant does not independently restrict those views.
Missing or malformed observations do not establish health. Radar suppresses these warnings when the observed generation is absent or differs from the resource generation, reconciliation is paused, or the resource is terminating. Matching generations only establishes that Strimzi processed that specification; runtime state can change before the next reconciliation. Intentional PAUSED/STOPPED states and task-count differences are not treated as failures. Failure onset is unknown because operator condition timestamps do not reliably establish when a task failed.
The source contract is Strimzi’s KafkaConnector status schema and connector management documentation. Discovery uses the served preferred version; partial-discovery recovery probes v1 and v1beta2.
diagnose supports KafkaConnector and KafkaConnect using cached operator status. KafkaConnect and related resource details can show up to five connector findings, linked by connector labels and a verified ownership chain. Findings keep the connector as their subject and do not change the viewed resource’s health. Missing findings do not establish recovery.
Unreadable owner links omit this context. MCP requires exact owner-object read permissions; the UI follows namespace-level Related Resources access, so their coverage may differ. Modern worker attribution also requires StrimziPodSet collection. See MCP semantics and access requirements.