# Deploy for Development

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: Deploy for Development
latest-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "true"
page-eol-date: December 22, 2024
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
docname: deployment-option/self-hosted/manual/production/dev-deployment
page-component-name: streaming
page-version: "23.3"
page-component-version: "23.3"
page-component-title: Streaming
page-relative-src-path: deployment-option/self-hosted/manual/production/dev-deployment.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/v/23.3/modules/deploy/pages/deployment-option/self-hosted/manual/production/dev-deployment.adoc
description: Steps to deploy a Redpanda sandbox cluster.
page-git-created-date: "2023-08-01"
page-git-modified-date: "2024-03-07"
support-status: past end-of-life
---

<!-- Source: https://docs.redpanda.com/streaming/23.3/deploy/deployment-option/self-hosted/manual/production/dev-deployment.md -->

You can deploy Redpanda using well-known configuration properties optimized for a development or test environment. This configuration uses less system resources and simplifies setup, but it’s not suitable for a production deployment. For example, in [development mode](https://docs.redpanda.com/streaming/23.3/reference/rpk/rpk-redpanda/rpk-redpanda-mode/#development-mode), the default `group_topic_partitions` is 3, and the default `storage_min_free_bytes` is 1 GiB. In production mode, the default `group_topic_partitions` is 16, and the default `storage_min_free_bytes` is 5 GiB.

> 📝 **NOTE**
>
> Development mode bypasses `fsync`, acknowledging messages before they’re stored to disk. This reduces the durability of messages, could cause potential data loss, and could give unrealistic performance data for a production environment.
>
> See [Deploy for Production](https://docs.redpanda.com/streaming/23.3/deploy/deployment-option/self-hosted/manual/production/production-deployment/) to deploy for a production environment.
>
> See [Redpanda Quickstart](https://docs.redpanda.com/streaming/23.3/get-started/quick-start/) to try out Redpanda in Docker.

## [](#prerequisites)Prerequisites

Make sure you meet the [hardware and software requirements](https://docs.redpanda.com/streaming/23.3/deploy/deployment-option/self-hosted/manual/production/requirements/).

### [](#tcpip-ports)TCP/IP ports

Redpanda uses the following default ports:

| Port | Purpose |
| --- | --- |
| 9092 | Kafka API |
| 8082 | HTTP Proxy |
| 8081 | Schema Registry |
| 9644 | Admin API and Prometheus |
| 33145 | internal RPC |

## [](#install-redpanda)Install Redpanda

Install Redpanda on each system you want to be part of your cluster. There are binaries available for Fedora/RedHat or Debian systems.

### Fedora/RedHat

```bash
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | \
sudo -E bash && sudo yum install redpanda -y
```

### Debian/Ubuntu

```bash
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | \
sudo -E bash && sudo apt install redpanda -y
```

## [](#install-redpanda-console)Install Redpanda Console

Redpanda Console is a developer-friendly web UI for managing and debugging your Redpanda cluster and your applications.

For each new release, Redpanda compiles the Redpanda Console to a single binary for Linux, macOS, and Windows. You can find the binaries in the attachments of each release on [GitHub](https://github.com/redpanda-data/console/releases).

### Fedora/RedHat

```bash
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | \
sudo -E bash && sudo yum install redpanda-console -y
```

### Debian/Ubuntu

```bash
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | \
sudo -E bash && sudo apt-get install redpanda-console -y
```

## [](#bootstrapping)Bootstrap broker configurations

Each broker requires a set of broker configurations that determine how all brokers communicate with each other and with clients. Bootstrapping a cluster configures the [listener](https://docs.redpanda.com/streaming/23.3/reference/glossary/#listener), seed-server, and [advertised listener](https://docs.redpanda.com/streaming/23.3/reference/glossary/#advertised-listener), which ensure proper network connectivity and accessibility.

Starting in version 23.3.8, `rpk` enhances the bootstrapping process with additional flags for configuring advertised listener addresses directly.

Use the [`rpk redpanda config bootstrap`](https://docs.redpanda.com/streaming/23.3/reference/rpk/rpk-redpanda/rpk-redpanda-config-bootstrap/) command to bootstrap Redpanda:

```bash
sudo rpk redpanda config bootstrap --self <listener-address> --advertised-kafka <advertised-kafka-address> --ips <seed-server1-ip>,<seed-server2-ip>,<seed-server3-ip> && \
sudo rpk redpanda config set redpanda.empty_seed_starts_cluster false
```

Replace the following placeholders:

-   `<listener-address>`: The `--self` flag tells Redpanda the interfaces to bind to for the Kafka API, the RPC API, and the Admin API. These addresses determine on which network interface and port Redpanda listens for incoming connections.

    -   Set the listener address to `0.0.0.0` to listen on all network interfaces available on the machine.

    -   Set the listener address to a specific IP address to bind the listener to that address, restricting connections to that interface.


-   `<advertised-kafka-address>`: The `--advertised-kafka` flag sets a different advertised Kafka address, which is useful for scenarios where the accessible address differs from the bind address.

    > ❗ **IMPORTANT**
    >
    > Redpanda does not allow advertised addresses set to `0.0.0.0`. If you set any advertised addresses to `0.0.0.0`, Redpanda will output startup validation errors.

-   `<seed-server-ips>`: The `--ips` flag lists all the seed servers in the cluster, including the one being started.

    > 📝 **NOTE**
    >
    > The `--ips` flag must be set _identically_ (with nodes listed in identical order) on each node.


Bootstrapping Redpanda updates your `/etc/redpanda/redpanda.yaml` configuration file:

`/etc/redpanda/redpanda.yaml`

```yaml
redpanda:
    data_directory: /var/lib/redpanda/data
    empty_seed_starts_cluster: false
    seed_servers:
        - host:
            address: <seed-server1-ip>
            port: 33145
        - host:
            address: <seed-server2-ip>
            port: 33145
        - host:
            address: <seed-server3-ip>
            port: 33145
    rpc_server:
        address: <listener-address>
        port: 33145
    kafka_api:
        - address: <listener-address>
          port: 9092
    admin:
        - address: <listener-address>
          port: 9644
    advertised_rpc_api:
        address: <listener-address>
        port: 33145
    advertised_kafka_api:
        - address: <advertised-kafka-address>
          port: 9092
```

### [](#recommendations)Recommendations

-   Redpanda Data strongly recommends at least three seed servers when forming a cluster. A larger number of seed servers increases the robustness of consensus and minimizes any chance that new clusters get spuriously formed after brokers are lost or restarted without any data.

-   It’s important to have one or more seed servers in each fault domain (for example, in each rack or cloud AZ). A higher number provides a stronger guarantee that clusters don’t fracture unintentionally.

-   It’s possible to change the seed servers for a short period of time after a cluster has been created. For example, you may want to designate one additional broker as a seed server to increase availability. To do this without cluster downtime, add the new broker to the [`seed_servers`](https://docs.redpanda.com/streaming/23.3/reference/node-properties/) property and restart Redpanda to apply the change on a broker-by-broker basis.


### [](#listeners-for-mixed-environments)Listeners for mixed environments

For clusters serving both internal and external clients, configure multiple listeners for the Kafka API to separate internal from external traffic.

For more details, see [Configure Listeners](https://docs.redpanda.com/streaming/23.3/manage/security/listener-configuration/).

## [](#start-redpanda)Start Redpanda

To start Redpanda:

```bash
sudo systemctl start redpanda-tuner redpanda
```

When a Redpanda cluster starts, it instantiates a controller Raft group with all the seed servers specified in the `--ips` flag. After all seed servers complete their startup procedure and become accessible, the cluster is then available. After that, non-seed servers start up and are added to the cluster.

## [](#start-redpanda-console)Start Redpanda Console

1.  Start Redpanda Console:

    ```bash
    sudo systemctl start redpanda-console
    ```

2.  Make sure that Redpanda Console is active and running:

    ```bash
    sudo systemctl status redpanda-console
    ```


## [](#verify-the-installation)Verify the installation

To verify that the Redpanda cluster is up and running, use `rpk` to get information about the cluster:

```bash
rpk cluster info
```

You should see a list of advertised addresses.

To create a topic:

```bash
rpk topic create <topic-name>
```

If topics were initially created in a test environment with a replication factor of `1`, use `rpk topic alter-config` to change the topic replication factor:

```bash
rpk topic alter-config <topic-names> --set replication.factor=3
```

## [](#perform-a-self-test)Perform a self test

To understand the performance capabilities of your Redpanda cluster, Redpanda offers built-in self-test features that evaluate the performance of both disk and network operations.

For more information, see [Disk and network self-test benchmarks](https://docs.redpanda.com/streaming/23.3/manage/cluster-maintenance/cluster-diagnostics/#self-test).

## [](#next-steps)Next steps

-   If clients connect from a different subnet, see [Configure Listeners](https://docs.redpanda.com/streaming/23.3/manage/security/listener-configuration/).

-   Observability is essential. See [Monitor Redpanda](https://docs.redpanda.com/streaming/23.3/manage/monitoring/).


## [](#suggested-reading)Suggested reading

-   [Configure Cluster Properties](https://docs.redpanda.com/streaming/23.3/manage/cluster-maintenance/cluster-property-configuration/)

-   [Redpanda Console Configuration](https://docs.redpanda.com/streaming/23.3/reference/console/config/)

-   [Work with Schema Registry](https://docs.redpanda.com/streaming/23.3/manage/schema-reg/)

-   [Work with HTTP Proxy](https://docs.redpanda.com/streaming/23.3/develop/http-proxy/)


## Suggested labs

-   [Disaster Recovery with Envoy and Shadowing](https://docs.redpanda.com/labs/docker-compose/envoy-shadowing/)
-   [Redpanda Iceberg Docker Compose Example](https://docs.redpanda.com/labs/docker-compose/iceberg/)
-   [Stream Jira Issues to Redpanda for Real-Time Metrics](https://docs.redpanda.com/labs/docker-compose/jira-metrics-pipeline/)
-   [Migrate Data with Redpanda Migrator](https://docs.redpanda.com/labs/docker-compose/redpanda-migrator/)
-   [Start a Single Redpanda Broker with Redpanda Console in Docker](https://docs.redpanda.com/labs/docker-compose/single-broker/)
-   [Start a Cluster of Redpanda Brokers with Redpanda Console in Docker](https://docs.redpanda.com/labs/docker-compose/three-brokers/)
-   [Set Up GitOps for the Redpanda Helm Chart](https://docs.redpanda.com/labs/kubernetes/gitops-helm/)
-   [Iceberg Streaming on Kubernetes with Redpanda, MinIO, and Spark](https://docs.redpanda.com/labs/kubernetes/iceberg/)
-   [Set Up MySQL CDC with Debezium and Redpanda](https://docs.redpanda.com/labs/docker-compose/cdc-mysql-json/)
-   [Set Up Postgres CDC with Debezium and Redpanda](https://docs.redpanda.com/labs/docker-compose/cdc-postgres-json/)

See more

[Search all labs](https://docs.redpanda.com/labs)