Overview
You can change a Pod's CPU, RAM and disk to match your workload without redeploying from scratch. This article explains how resizing works in the ALYPOD Console and what to expect during the process.
Before you begin
- A Pod in the ALYPOD Console.
- A snapshot taken first — resizing reboots the Pod and is best done with a rollback point available.
- Ideally, resize during a maintenance window.
How resizing works
- CPU/RAM: the Pod is stopped, resources are reassigned, and it starts again. Your IP addresses and disk contents are preserved.
- Disk: the root volume can only usually be grown, not shrunk. Growing can require an extra reboot while the filesystem expands.
- Billing: the new price applies from the moment of the change, prorated by your billing cycle.
Steps
- Sign in to account.alypod.com and open the ALYPOD Console.
- Select your Pod and open the Resize tab.
- Pick a larger plan (or edit individual resources if offered).
- Review the new price and confirm.
- Wait for the status to return to Running.
- Verify the new resources:
bash
nproc # CPU cores
free -h # RAM
df -h / # disk space
If the disk grew but the filesystem did not expand automatically, grow it manually:
```bash
For LVM-based installs
sudo growpart /dev/sda 3 sudo pvresize /dev/sda3 sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv ```
Downgrading
If you need to shrink, you often cannot reduce resources below the current disk usage. Check usage first, remove data, then pick a smaller plan. Take a snapshot before downgrading.
Troubleshooting
- Problem: Pod does not boot after resizing. Solution: check the VNC tab;
if the filesystem needs repair, boot rescue mode and run
fsck. - Problem: filesystem still shows the old size. Solution: you skipped the grow commands above — run them again.
Related articles
- [Creating and restoring snapshots]
- [Dedicated CPU Pods explained]
- [Accessing rescue mode]
