Resize Registry Storage
Registry storage resizing allows you to increase the storage capacity of an existing Container Registry without disrupting your images or workflows.
CloudRaya Container Registry is designed to scale as your container image usage grows.
When to Resize Registry Storage
You should consider resizing your registry storage when:
- Image pushes start failing due to storage limits
- CI/CD pipelines produce larger or more frequent images
- You retain multiple versions or tags for rollback
- Vulnerability scans and build layers increase storage usage
📌 Storage resizing is non-destructive and does not affect existing images.
Supported Resize Behavior
CloudRaya supports storage expansion only.
| Action | Supported |
|---|---|
| Increase storage | ✅ Yes |
| Decrease storage | ✅ Yes |
| Data preserved | ✅ Yes |
| Downtime required | ❌ No |
| Service interruption | ❌ No |
Storage resizing is seamless and applied without affecting existing images, repositories, or running workloads.
How Storage Resize Works
- Storage capacity can be increased or decreased at any time
- Changes take effect immediately
- Existing images remain intact as long as usage stays within the new limit
- No re-authentication or reconfiguration is required
📌 Important: When downsizing, ensure current storage usage does not exceed the new limit.
How to Resize Registry Storage
- Go to Dashboard → Storage → CloudRaya Container Registry
- Click View Detail on the target registry
- Locate the Storage Usage section
- Click Upgrade
- Select the additional storage amount
- Confirm the upgrade
The new storage capacity is applied immediately.
Storage Adjustment Rules
- Storage is adjusted in fixed increments of 10 GB
- Both upgrade and downgrade follow the same increment rule
- You can freely move between sizes (example):
10 GB ⇄ 20 GB ⇄ 30 GB ⇄ 50 GBBilling & Cost Awareness
Storage upgrades are billed based on:
- Additional storage size
- Hourly billing model
- Active usage duration
Important notes:
- The first 10 GB is free for every account
- Charges apply only to storage above the free tier
- Billing starts immediately after upgrade confirmation
📌 Deleted images do not reduce allocated storage or billing.
What Happens After Upgrade
After resizing:
- Existing images remain unchanged
- New images can be pushed immediately
- CI/CD pipelines continue without interruption
- No reconfiguration is required on Docker or Kubernetes
Storage expansion is transparent to all consumers.
Downsize Considerations
Before reducing storage capacity:
- Verify current storage usage
- Remove unused images or tags if needed
- Ensure CI/CD pipelines will not exceed the new limit
If usage exceeds the selected size, the resize action will be blocked.
Best Practices
- Monitor registry storage usage regularly
- Resize storage proactively based on actual usage
- Remove unused and outdated image tags
- Use separate registries for production and non-production
- Enable Tag Immutability for production registries