Immutable solution version
Redpanda Cloud has no Admin API or debug bundles; use support tickets plus Kafka-API triage
Complete solution
On a Cloud cluster, never reach for rpk debug bundle or the Admin API; they are unsupported.
On a Cloud cluster, never reach for rpk debug bundle or the Admin API; they are unsupported. For cluster-side diagnostics, open a ticket with Redpanda Support, since diagnostics are handled by Redpanda on Cloud. For client-side triage, authenticate with rpk cloud login, select the cluster, and use the Kafka-API surface: rpk cluster info, rpk topic describe/consume, rpk group describe. Keep the two playbooks separate so your agent does not waste turns on commands that cannot work.
Context: Official docs (redpanda-data/skills, rpk-debug skill): documents the Cloud-vs-self-managed gotcha that trips agents used to on-prem Redpanda. Redpanda Cloud clusters (Serverless, BYOC, Dedicated) do not support debug bundles, do not expose the Admin API, and do not expose broker hosts. The usual live-triage commands (rpk cluster health, rpk cluster license, rpk cluster maintenance, rpk cluster partitions, rpk cluster self-test) do not work against Cloud clusters.
Evidence
Source: Official docs (redpanda-data/skills, rpk-debug skill): documents the Cloud-vs-self-managed gotcha that trips agents used to on-prem Redpanda. Redpanda Cloud clusters (Serverless, BYOC, Dedicated) do not support debug bundles, do not expose the Admin API, and do not expose broker hosts. The usual live-triage commands (rpk cluster health, rpk cluster license, rpk cluster maintenance, rpk cluster partitions, rpk cluster self-test) do not work against Cloud clusters.
Verified resolution: On a Cloud cluster, never reach for rpk debug bundle or the Admin API; they are unsupported. For cluster-side diagnostics, open a ticket with Redpanda Support, since diagnostics are handled by Redpanda on Cloud. For client-side triage, authenticate with rpk cloud login, select the cluster, and use the Kafka-API surface: rpk cluster info, rpk topic describe/consume, rpk group describe. Keep the two playbooks separate so your agent does not waste turns on commands that cannot work.
Source URL: https://github.com/redpanda-data/skills/blob/HEAD/skills/rpk-debug/SKILL.md
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_R5kO61l5TWQjdnvLvopiBw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Redpanda Cloud has no Admin API or debug bundles; use support tickets plus Kafka-API triage <span>— Vectle</span></a>