Deploy

• Choose a Deployment Option

  • Self-Hosted

    • Kubernetes

      • Kubernetes Cluster Requirements

        This topic is a checklist with the prerequisites and system requirements for installing production Redpanda in a Kubernetes cluster using the Helm chart.

      • Kubernetes Production Deployment

        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.

      • Best Practices

        This topic explains Redpanda's tips and recommendations for Kubernetes deployments.

      • Tune Worker Nodes

        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.

      • Deploy Redpanda

        This topic describes how to use the Redpanda Helm chart to deploy a Redpanda cluster in Kubernetes.

    • Manual

      • Deploy for Production

        You can use rpm to setup a production cluster of Redpanda using our default deployment or writing a custom deployment script.

      • Automate Deployment for Production

        You can use automation tools in your environment such as Terraform and Ansible to deploy Redpanda for production.

      • Configure Node Properties

        When you install Redpanda, a redpanda.yaml file 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 data_directory or node_id (when specified).

      • High Availability

        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.

      • Sizing Use Cases

        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.

      • Sizing Guidelines

        For best performance, size your Redpanda cluster to handle the volume of data being produced, replicated, and consumed.

• Cloud

  • Redpanda Cloud Overview

    A high-level overview about the features that Redpanda Cloud offers.

  • Redpanda Dedicated

    • Create Clusters

      To create a Redpanda cluster in the Dedicated cloud, log in to the Redpanda Cloud, add a namespace, then follow the steps for creating a Dedicated cluster.

    • VPC Peering

      A VPC peering connection is a networking connection between two VPCs. This connection allows the VPCs to communicate with each other as if they were within the same network. A route table routes traffic between the two VPCs using private IPv4 addresses.

  • Create a BYOC Cluster on AWS

    To create a Redpanda cluster in your own AWS cloud, log in to the Redpanda Cloud UI and create a namespace, then follow the steps for creating a Bring your own cloud (BYOC) cluster.

  • Create a BYOC Cluster on GCP

    To create a Redpanda cluster in your own GCP cloud, log in to the Redpanda Cloud UI and create a namespace, then follow the steps for creating a Bring your own cloud (BYOC) cluster.

  • Create a Topic

    Create a Topic for your cluster.

  • Managed Connectors

    • Create a S3 Sink Connector

      The Amazon S3 Sink connector stores Apache Kafka messages in an AWS S3 bucket.