Skip to content

Configuring Console when deployed using operator chart #1272

@qlikcoe

Description

@qlikcoe

There are some contradictions related to the Console configuration.

  1. This page says:
When you deploy a Redpanda cluster using the [Redpanda Operator or Redpanda Helm chart](https://docs.redpanda.com/current/deploy/redpanda/kubernetes/k-production-deployment/), 
Redpanda Console is automatically deployed alongside your cluster. 

I can confirm, indeed, when I deployed the operator, the Console CR was created and console was successfully deployed along with the rest of the components. All the values like brokers etc are nicely pre-populated and console works right out of the box.

  1. This page, for the operator says:
Configure Redpanda Console in the console section of your Redpanda custom resource:

And right below that statement there is a code snippet for the Console CR, not the Redpanda one.

  1. The API doc for the RedpandaClusterSpec says that console is Deprecated: Use the dedicated Console CRD.

The question is - how do we configure the console if the Console CR is automatically created by the operator? I need to make just small adjustments, while I don't want to loose any pre-populated parameters.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions