Skip to content

tf: smaller supernode droplets (s-8vcpu-16gb-480gb-intel) #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
qu0b merged 1 commit into from
Sep 23, 2026
Merged

tf: smaller supernode droplets (s-8vcpu-16gb-480gb-intel) #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion terraform/devnet-0/digitalocean.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ variable "digitalocean_ssh_key_name" {

variable "digitalocean_supernode_size" {
type = string
default = "s-8vcpu-32gb-640gb-intel"
default = "s-8vcpu-16gb-480gb-intel"

@redpandabot redpandabot Bot Sep 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 in-place resize of existing 640 GB droplets would fail — DO cannot shrink disk

digitalocean_droplet.main sets resize_disk = true, so if this is applied to an existing devnet-0 fleet still running the 640 GB slug, terraform will attempt an in-place resize with a disk decrease, which the DigitalOcean API rejects. Fine for a fresh apply/destroy-recreate cycle; worth confirming the devnet is rebuilt rather than resized in place.

}

variable "digitalocean_fullnode_size" {
Expand Down
Loading