Redpanda Console

    This topic contains information about deploying, configuring, and using Redpanda Console. Some features are only available if you provide an Enterprise license key. The documentation flags configurable features that require a license.

  • Features
    • Kafka Connect

      Connecting one or more Kafka connect clusters with your Redpanda Console deployment.

    • Record Deserialization

      Explanation how Record deserialization in Redpanda Console works and what encodings it supports.

    • Schema Registry

      Configuring schema registry in Redpanda Console.

    • Protobuf Deserialization

      Configuring Protobuf deserialization to decode encoded Kafka records in Redpanda Console.

    • Topic Documentation

      Embed your Kafka topic specific documentation into the Redpanda Console UI by linking a Git repository that contains the topics' documentation files.

    • Programmable Push Filters

      Filtering Kafka records in Console's message viewer based on your provided JavaScript code.

    • HTTP Path Rewrites

      If you want to host Redpanda Console under a sub-path rather than the root path, you need to configure this. This page explains how you can configure Console to comply with your URL rewrites.

  • Single Sign On
    • Authentication

      Configure authentication with external identity providers such as Google, GitHub or Okta in Redpanda Console.

    • Authorization

      Configure authentication with external identity providers such as Google, GitHub or Okta in Redpanda Console.

    • GitHub SSO Setup

      Configure authentication with external identity providers such as Google, GitHub or Okta in Redpanda Console.

    • Google SSO Setup

      Configure authentication with external identity providers such as Google, GitHub or Okta in Redpanda Console.

    • Okta SSO Setup

      Configure authentication with external identity providers such as Google, GitHub or Okta in Redpanda Console.

    • Generic OIDC

      Integrate your Redpanda Console authentication with any identity provider that supports an OIDC-compatible protocol.

  • Reference