Freedom251 › Container Registries
SUSE Private Registry
What SUSE Private Registry is
SUSE Private Registry is an on-premises container registry for SUSE customers and integration with other SUSE products. Based on Harbor, it is delivered as OCI containers for Kubernetes, with Helm handling installation and management. Documented prerequisites are Kubernetes 1.33, 1.34, or 1.35, Helm 3.2.0 or later, persistent volume provisioner support, and an active qualifying subscription. Administrators can use a web interface or command line to manage settings, users, project quotas, read-only mode, and image replication. Authentication, authorization, and role-based access control are included. Trivy provides vulnerability scanning, with SUSE Security as an alternative. The registry stores, distributes, and verifies Cosign signatures but does not sign images; Notary is unsupported. Policy-based pull and push replication connects deployments. High availability needs separately supplied database, cache, storage, and ingress or load-balancing components. Pricing is on request.
Who it suits
It suits SUSE customers running container infrastructure on Kubernetes with a qualifying subscription. Teams needing registry administration, access controls, scanning, and replication can consider it.
What it does well
- Built on Harbor core features
- Supports web and command-line administration
- Includes role-based access control
- Provides Trivy vulnerability scanning
- Supports policy-based image replication
What to know first
- Requires an active qualifying subscription
- Needs Kubernetes 1.33, 1.34, or 1.35
- High availability requires separate components
- Does not sign images itself
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| SUSE Private Registry subscription | Requires an active qualifying subscription, such as Rancher Suite or SUSE Private Registry Add-on | On request |
As documentation.suse.com lists them, read 11 Oct 2026. The maker's own page has the final word.
Verdict
SUSE Private Registry provides an on-premises Harbor-based registry with access control, scanning, signatures, and replication. Its Kubernetes prerequisites, subscription requirement, and separately supplied high-availability components shape deployment planning.
Facts from SUSE Private Registry's own pages
- Access controls
- The registry includes authentication, authorization, and role-based access control. · documentation.suse.com, 11 Oct 2026
- Deployment
- It is delivered as OCI containers and is expected to run on a Kubernetes cluster, with Helm used for installation and management. · documentation.suse.com, 11 Oct 2026
- Founded
- 1992 · documentation.suse.com, 28 Sept 2026
- Harbor foundation
- The product is based on the Harbor project and includes Harbor’s core features. · documentation.suse.com, 11 Oct 2026
- Hardened images
- SUSE says its registry container images are hardened, based on SUSE Linux Enterprise Base Container Images, signed with Cosign, and published with SLSA attestations. · documentation.suse.com, 11 Oct 2026
- Headquarters
- Luxembourg, Luxembourg · documentation.suse.com, 28 Sept 2026
- High availability
- High availability requires separately provided HA PostgreSQL, Valkey or Redis, persistent storage or supported object storage, and an HA ingress controller or load balancer. · documentation.suse.com, 11 Oct 2026
- Image signing
- The registry can store, distribute, and verify Cosign signatures, but it does not sign images itself and Notary is not included or supported. · documentation.suse.com, 11 Oct 2026
- Purpose
- SUSE Private Registry is an on-premises container registry designed for SUSE customers and integration with other SUSE products. · documentation.suse.com, 11 Oct 2026
- Rancher identity
- The documentation describes configuring Rancher as an OIDC identity provider so users can authenticate to the registry with Rancher credentials. · documentation.suse.com, 11 Oct 2026
- Registry management
- Administrators can use a web interface or command line to manage settings, users, project quotas, read-only mode, and image replication. · documentation.suse.com, 11 Oct 2026
- Replication
- It supports policy-based pull and push replication across multiple Private Registry deployments. · documentation.suse.com, 11 Oct 2026
- Requirements
- The documented prerequisites include Kubernetes 1.33, 1.34 or 1.35, Helm 3.2.0 or later, persistent volume provisioner support, and an active subscription. · documentation.suse.com, 11 Oct 2026
- Subscription access
- Installation requires a qualifying subscription and SUSE Customer Center mirroring credentials; SUSE lists Rancher Suite and the SUSE Private Registry Add-on as examples. · documentation.suse.com, 11 Oct 2026
- Support
- SUSE states that the product follows the same support policy as other Rancher Prime add-ons. · documentation.suse.com, 11 Oct 2026
- Vulnerability scanning
- Trivy is included for image vulnerability scanning, and SUSE Security can be added or used instead. · documentation.suse.com, 11 Oct 2026
Where SUSE Private Registry stands on Freedom251
- Container Registries#51 of 60