This topic is a checklist with the prerequisites and system requirements for installing production Redpanda in a Kubernetes cluster using the Helm chart.
Redpanda offers two tools for deploying Redpanda clusters in Kubernetes:
Redpanda Helm chart (recommended)
Redpanda Operator (not recommended for new deployments)
Redpanda recommends the Helm chart for all new deployments. As a result, the Kubernetes documentation in this section is for Helm chart deployments.
This topic explains Redpanda's tips and recommendations for Kubernetes deployments.
To get the best performance from your hardware, set Redpanda to production mode on each worker node and run the auto-tuning tool. The auto-tuning tool identifies the hardware configuration on your worker node and optimizes the Linux kernel to give you the best performance.
This topic describes how to use the Redpanda Helm chart to deploy a Redpanda cluster in Kubernetes.
You can use
rpmto setup a production cluster of Redpanda using our default deployment or writing a custom deployment script.
You can use automation tools in your environment such as Terraform and Ansible to deploy Redpanda for production.
When you install Redpanda, a
redpanda.yamlfile is installed on each node in
/etc/redpanda. This file contains node configuration properties. A node property is one that can be set differently from node to node, such as
Redpanda is designed to ensure data integrity and high availability (HA), even at high-throughput levels. This section explains the trade-offs with different configurations.
The following scenarios provide estimates and advice for sizing Redpanda clusters for different throughput and retention use cases in your data center and in the cloud.
For the best performance, size your Redpanda cluster to handle the volume of data being produced, replicated, and consumed.