Repositories
OCI- and Docker-compatible organization repositories, including nested paths. You create them public or private and use them across the organization.
Registry
Your registry for images and Helm charts.
OCI- and Docker-compatible repositories for images and Helm charts. Push from CI, pull into managed Kubernetes, with Loopback RBAC and robot accounts.
Access
Familiar clients. The same platform.
Push and pull run through ordinary OCI and Docker workflows. Familiar clients, Loopback RBAC, and robot accounts. The Registry is organization-wide.
OCI and Docker
Images and Helm charts sit in the Registry as OCI artifacts. Push and pull run with familiar clients.
Robot accounts
Robot accounts handle machine push from CI. Images from the pipeline land in the organization-wide Registry.
Visibility
You decide for each repository whether it is public or private. That applies to images and Helm charts.
Organization-wide
The Registry belongs to the whole organization. Clusters and Bundles in the organization use the same Registry.
Loopback RBAC
Loopback RBAC governs access centrally, as elsewhere on the platform. Permissions apply to people and robot accounts.
Location
The Registry is located in Germany, and so are all your images and Helm charts.
From pipeline to cluster.
Push from CI remains the normal path. Bundles can also place images in the Registry automatically.
01
Repository
Create OCI- and Docker-compatible repositories, including nested paths. Visibility is public or private. The Registry is organization-wide.
02
Access
Loopback RBAC for people. Robot accounts and credentials for CI and cluster pull.
03
Push
You push images and Helm charts from the pipeline, with familiar clients.
04
Pull
Pull artifacts into managed Kubernetes.
What you can do
Repositories, credentials, and content in the organization-wide registry.
Credentials
Credentials with pull, push, and delete rights. That is how you control machine access to the organization's repositories.
Robot accounts
Machine access for CI and cluster pull. Robot accounts push from the pipeline and pull images into managed Kubernetes.
Content browser
Browse folders and tags and see which images and charts live in the Registry.
One registry for the organization.
The Registry belongs to the organization. Clusters and Bundles use it. Loopback RBAC applies centrally, as elsewhere on the platform.
Organization
Account, teams, and roles. The frame for every resource.
Registry
One registry for the organization. Repositories public or private, including nested paths.
Clusters and Bundles
Pull images into managed Kubernetes. Bundles land images in the Registry automatically.
The facts.
| API | OCI and Docker |
|---|---|
| Artifacts | Images and Helm charts |
| Visibility | Public or private |
| Access | Loopback RBAC and robot accounts |
| Scope | Organization-wide |
| Location | Germany |
| SLA | 99.5% availability |
Keep working in the same organization.
Your clusters pull images straight from the organization Registry. Object Storage and Bundles work in the same account.
Images and charts at the storage price.
The Registry is 0.05€ per GB per month, billed hourly. Everything lives in the same account as the cluster.
Registry
0.05€
per GB per month, billed hourly Based on 720 hours
- OCI and Docker
- Images and Helm charts
- Organization-wide
- Loopback RBAC
- Robot accounts
- Located in Germany
FAQ
Is the Registry OCI- and Docker-compatible?
Yes. Public and private repositories, Loopback RBAC, and robot accounts are included. You push images and Helm charts with familiar clients.
Can repositories be public and private?
Yes. You decide for each repository whether it is public or private.
How is access managed?
Access runs through Loopback RBAC. Robot accounts and credentials cover machine push and pull.
Where are images stored?
The Registry is located in Germany.
How is Registry storage billed?
You pay per stored GB. Traffic is billed separately by usage.