# Redpanda Console Linux Requirements and Recommendations

> 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: Redpanda Console Linux Requirements and Recommendations
latest-redpanda-tag: v26.1.9
latest-console-tag: v3.7.3
latest-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "false"
page-eol-date: March 31, 2027
latest-connect-version: 4.93.0
docname: console/linux/requirements
page-component-name: streaming
page-version: "26.1"
page-component-version: "26.1"
page-component-title: Streaming
page-relative-src-path: console/linux/requirements.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/main/modules/deploy/pages/console/linux/requirements.adoc
description: System requirements and recommendations for deploying Redpanda Console on Linux in production.
page-git-created-date: "2025-08-15"
page-git-modified-date: "2025-08-15"
support-status: supported
---

<!-- Source: https://docs.redpanda.com/streaming/current/deploy/console/linux/requirements.md -->

This page provides the system requirements and recommendations for deploying Redpanda Console on Linux in production environments.

## [](#operating-system)Operating system

-   **Linux**: All major distributions (Ubuntu, CentOS, RHEL, Debian)

-   **Container platforms**: Docker, Kubernetes, OpenShift

-   **Cloud platforms**: AWS, GCP, Azure


## [](#cpu-and-memory)CPU and memory

-   **CPU**: Minimum 2 cores. Recommended 4+ cores for production.

-   **Memory**: Minimum 1 GiB per replica. Recommended 1-2 GiB for most workloads, 2 GiB+ for high concurrency or large data sets.


## [](#storage)Storage

-   **Minimum**: 1 GiB available disk space


## [](#network-requirements)Network requirements

-   **Redpanda connectivity**: TCP access to Redpanda brokers on configured ports

-   **Web interface**: HTTP/HTTPS access for users (typically port 8080 or 443)

-   **Schema Registry**: TCP access to Schema Registry, if used


## [](#security-considerations)Security considerations

-   **TLS encryption**: Configure TLS for all network communications

-   **Authentication**: Set up appropriate authentication mechanisms

-   **RBAC**: Implement role-based access control where supported

-   **Firewall rules**: Configure appropriate firewall rules to restrict access


## [](#scaling-and-high-availability)Scaling and high availability

-   Deploy multiple Redpanda Console replicas for high availability and rolling updates.

-   Use pod anti-affinity to spread replicas across nodes.

-   For production, run at least two replicas.


## [](#separate-node-deployment)Separate node deployment

Run Redpanda Console on separate nodes from Redpanda brokers for resource isolation and operational independence.

## [](#schema-registry-integration)Schema Registry integration

-   Allocate extra memory for schema caching if using Schema Registry.

-   Ensure reliable network connectivity and configure authentication as needed.


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

-   [Deploy Redpanda Console on Linux](https://docs.redpanda.com/streaming/current/deploy/console/linux/deploy/)

-   [Configure Redpanda Console](https://docs.redpanda.com/streaming/current/console/config/configure-console/)


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

-   [Redpanda Console Security](https://docs.redpanda.com/streaming/current/console/config/security/)