Redpanda Operator Helm Chart Specification

Passes additional flags to the Redpanda Operator at startup. Additional flags include: - --additional-controllers: Additional controllers to deploy. Valid values are nodeWatcher or decommission. For more information about the Nodewatcher controller, see Install the Nodewatcher controller. For more information about the Decommission controller, see Use the Decommission controller.

Default: []

Sets affinity constraints for scheduling Pods that run the Redpanda Operator. For details, see the Kubernetes documentation.

Default: {}

Sets the Kubernetes cluster domain.

Default: "cluster.local"

Additional labels to add to all Kubernetes objects. For example, my.k8s.service: redpanda-operator.

Default: nil

Configuration for the Kubernetes Controller Manager used by Redpanda Operator. The Controller Manager is a component of the Kubernetes control plane that runs controller processes. These controllers are background threads that handle the orchestration and operational logic of Kubernetes, ensuring the desired state of the cluster matches the observed state.

Default:

Configuration for health checking.

Default:

Sets the address for the health probe server to listen on.

Default: ":8081"

Configuration for leader election, which is a process that ensures only one instance of the controller manager is active at a time. This is critical for high availability and to prevent split-brain scenarios in a distributed system.

Default:

Enables leader election.

Default: true

Sets the name of the resource lock for the leader election process.

Default: "aa9fc693.vectorized.io"

Configuration for the metrics endpoint.

Default:

Sets the address for the metrics server to bind to.

Default: "127.0.0.1:8080"

Configuration for webhooks, such as the port they listen on. Webhooks are HTTP callbacks that receive and process data in response to events.

Default: {"port":9443}

Sets the port for the webhook server to listen on.

Default: 9443

Configuration for the Redpanda configurator, a component for managing Redpanda configuration.

Default:

Sets the pullPolicy for the Redpanda configurator image.

Default: "IfNotPresent"

Sets the repository in which the Redpanda configurator image is available.

Default:

Overrides the redpanda-operator.fullname template.

Default: ""

Container image settings.

Default:

Sets the pullPolicy for the redpanda-operator image.

Default: "IfNotPresent"

Sets the repository from which to pull the redpanda-operator image.

Default:

Pull secrets may be used to provide credentials to image repositories See the Kubernetes documentation.

Default: []

Configuration for the kube-rbac-proxy, a component that provides an HTTP proxy to perform authorization checks.

Default:

Sets settings for pulling the kube-rbac-proxy image.

Default:

Sets the pullPolicy for kube-rbac-proxy image

Default: "IfNotPresent"

Sets the repository in which the kube-rbac-proxy image is available.

Default:

Sets the kube-rbac-proxy image tag.

Default: "v0.14.0"

Log level Valid values (from least to most verbose) are: fatal, panic, error, info and debug.

Default: "info"

Configuration for monitoring.

Default:

Deploys the Prometheus community Helm chart.

Default: false

Creates a ServiceMonitor that can be used by Prometheus-Operator or VictoriaMetrics-Operator to scrape the metrics.

Default: false

Overrides the redpanda-operator.name template.

Default: ""

Node selection constraints for scheduling Pods on specific nodes. For details, see the Kubernetes documentation.

Default: {}

Default: {}

Default: {}

Role-based Access Control (RBAC) configuration for the Redpanda Operator.

Default:

Enables the creation of additional RBAC roles.

Default: true

Creates additional RBAC cluster roles that are needed to run additional controllers using additionalCmdFlags.

Default: false

Create RBAC cluster roles needed for the Redpanda Helm chart’s `rbac.enabled' feature.

Default: false

Sets the number of instances of the Redpanda Operator to deploy. Each instance is deployed as a Pod. All instances are managed by a Deployment resource.

Default: 1

Sets resources requests/limits for Redpanda Operator Pods. By default requests and limits are not set to increase the chances that the charts run on environments with few resources, such as Minikube. To specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after resources.

Default: {}

Sets the scope of the Redpanda Operator. Valid values are Cluster or Namespace. The Cluster scope is deprecated because it deploys the deprecated version of the Redpanda Operator. Use the default Namespace scope. In the Namespace scope, the Redpanda Operator manages Redpanda resources that are deployed in the same namespace as itself.

Default: "Namespace"

Service account management.

Default: {"create":true,"name":null}

Specifies whether a service account should be created.

Default: true

The name of the service account to use. If not set and serviceAccount.create is true, a name is generated using the redpanda-operator.fullname template.

Default: nil

Taints to be tolerated by Pods. For details, see the Kubernetes documentation.

Default: []

Specifies whether to create Webhook resources both to intercept and potentially modify or reject Kubernetes API requests as well as authenticate requests to the Kubernetes API. Only valid when scope is set to Cluster.

Default: {"enabled":false}

Creates the Webhook resources.

Default: false

Default: "webhook-server-cert"