Streaming

Redpanda Console Linux Requirements and Recommendations

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

Operating system

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

  • Container platforms: Docker, Kubernetes, OpenShift

  • Cloud platforms: AWS, GCP, Azure

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

  • Minimum: 1 GiB available disk space

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

  • 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

  • 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

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

Schema Registry integration

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

  • Ensure reliable network connectivity and configure authentication as needed.

Next steps

Suggested reading