Manage Debug Bundles in Redpanda Console

The Redpanda Operator deploys Redpanda Console v2.x, not v3.x.

Redpanda Console v3 is not yet available when deploying with the Redpanda Operator. The Redpanda Operator continues to deploy Redpanda Console v2. To try Redpanda Console v3 in Kubernetes, you can deploy Redpanda using the Redpanda Helm chart instead of the Redpanda Operator.

Redpanda Console configuration syntax varies by major version. Before configuring, determine which version you’re using:

# Check console version from deployment
kubectl get deployment -n <namespace> redpanda-console -o jsonpath='{.spec.template.spec.containers[0].image}'

# Or check from running pod
kubectl get pod -n <namespace> -l app.kubernetes.io/name=console -o jsonpath='{.items[0].spec.containers[0].image}'

# Or check from console logs
kubectl logs -n <namespace> -l app.kubernetes.io/name=console | grep "started Redpanda Console"

If you see output like redpandadata/console:v2.8.0, you’re using Redpanda Console v2.x. If you see redpandadata/console:v3.0.0, you’re using Redpanda Console v3.x.

This feature requires an enterprise license. To get a trial license key or extend your trial period, generate a new trial license key. To purchase a license, contact Redpanda Sales.

If Redpanda Console has enterprise features enabled and it cannot find a valid license, it redirects you to the license expiration landing page, and all other access is restricted.

Learn how to generate, download, and delete debug bundles in Redpanda Console for comprehensive cluster diagnostics.

When your cluster is unhealthy, Redpanda Console displays debugging data on the Overview page. If you are logged in as an admin user, you also get a link to generate a debug bundle.

degraded cluster

Prerequisites

Generate a debug bundle

You can generate a debug bundle for all brokers in the cluster and download it onto your local computer for inspection.

Only one debug bundle can exist at a time. If you generate a new debug bundle, any existing bundle from a previous run will be automatically deleted.

  1. Click Debug bundle.

  2. Click Generate default.

  3. Wait until the process is complete.

  4. Click debug-bundle.zip to download the bundle on your local computer.

  5. Unzip the file to inspect the contents.

For guidance on reading the debug bundle, see Inspect a Debug Bundle.

Delete a debug bundle

To manually delete a debug bundle:

  1. Click Debug bundle.

  2. Click the trash icon next to debug-bundle.zip to delete the bundle.

Next steps