|Index|Getting started with SUSE Private Registry|Requirements
Applies to SUSE Private Registry 1.0

2 Requirements

This section describes the minimum platform prerequisites and recommended production sizing for SUSE Private Registry.

2.1 Prerequisites

  • A Kubernetes cluster version 1.20 or higher

  • Helm version 3.2.0 or higher

  • Persistent Volume (PV) provisioner support in your infrastructure

  • An active subscription for SUSE Private Registry

2.2 Hardware and sizing recommendations

Use these values as a production starting point. Tune based on retention policy, image churn, scan concurrency and replication traffic. ==== Cluster Baseline

ScopeRecommended starting point

Worker nodes

3 worker nodes minimum

Node shape

4 vCPU and 16 GiB RAM per node minimum

Preferred node shape

8 vCPU and 32 GiB RAM per node for higher scan and push concurrency

These recommendations align with Rancher guidance for RKE2 Kubernetes. For details, see RKE2 Kubernetes installation requirements.

2.2.1 Persistent Storage Baseline

ComponentDefault chart sizeRecommended starting size

Registry data

5 Gi

500 Gi to 1 Ti

Trivy cache and DB

5 Gi

20 Gi to 50 Gi

Jobservice logs

1 Gi

10 Gi

Internal PostgreSQL (if used)

1 Gi

20 Gi minimum

Internal Valkey (if used)

1 Gi

20 Gi minimum

The chart defaults are installation-oriented and should not be used as long-term production capacity values.