This feature is quite important that can limit the downgrade of water drops

fall guys

This "idea" shouldn't still just be an idea... how long does it take a company as big as DigitalOcean to implement such a simple and widely requested feature.

The complexity of adding such a feature isn't even that difficult. It's not like user are asking for a super advanced

Option 1:

DigitalOcean can simply make it so users can go into the current droplet, go to destroy the droplet and choose to "Reserve IP" as shown by clicking here

If DigitalOcean are worried about users hoarding IP's you can add the following:

• You are only allowed a maximum of 5 reserved IP's at any one time.

If DigitalOcean are worried that they'll be making losses because too many customers are reserving IP's, simply add the following:

• If a reserved IP is not attached to a droplet, you will be charged at $5 per month, per IP that is not being used.

If DigitalOcean are still worried they might run out of IP's then add the following:

• You can only reserve an IP for 3 months, if the IP is not used within 3 months it gets returned to the public pool of IPs.
  

Option 2:

DigitalOcean already has the ability to create system backups, it already has the ability to delete droplets, resize droplets and create droplets from backup. Therefore you can use all of those functions to create a new feature of "Backup & Downsize"

You simply warn the user that this downsizing will take much longer than a regular resizing, and much longer than a regular backup because the feature has to backup, delete, reserve, create, restore.

The feature automatically run the following in sequence:

1. Turn off the current droplet

2. Create a backup of the current droplet

3. Reserve the IP of the current droplet

4. Destroy the current droplet

5. Create a new droplet with the reserved IP, new droplet type/size restoring the backup that the feature just created.

This therefore achieves the same function as #1 but makes it an automatic process.

A fair amount of users who have commented / voted on this issue will be developers themselves, just like myself and we're all very aware that this sort of task isn't overly complex so it brings up a lot of questions as to why this hasn't been implemented still...

Thanks

How many different times/ways do we have to ask for this before DigitalOcean will do something? This is unacceptable

All asking for the same thing, it's been years now:
https://ideas.digitalocean.com/ideas/DO-I-2609
https://ideas.digitalocean.com/ideas/DO-I-1028

https://ideas.digitalocean.com/ideas/DO-I-2000
https://ideas.digitalocean.com/ideas/DO-I-2027

I guess DigitalOcean doesn't care about improving the offerings over time per customer feedback. Frustrating.

Resizing a server does not change its IP address

I would like to run authoritative name servers on Digital Ocean but without static IPs, this does not work, does it ? Because with Floating IPs the server would not use the floating IP as source ip, correct ?

I total agreed this feature is important due to the limitation of droplet downgrade. It could either coverted to floating IP or transfer to the new droplet.

Why is this not solved by the floating IPs?? I do not get what this issue exactly requests.

Seriously need this feature. Floating IPs is not a solution for this. Many of us use VPN's for securing our infra with whitelisting IP addresses.

How is this still a problem after all the years it's been requested.

use floating IP address, this idea is not good

How does the Floating IP feature not cover this?

Just use float IP or the load balancer (it comes with a static ip)

What it comes down to is the use of floating IPs and rDNS records it seems. Reverse DNS lookup only points to the droplet IP, which of course means that all mail from the server/droplet will likely get spammed, even with proper SPF, DKIM and DMARC setup. Currently you can't seem to have both worlds - floating IPs for juggling droplets AND email deliverability via rDNS on the floating IP. The email looks like it's coming from a different domain than the FQDN. 

It's a pain really. I've just accidentally destroyed my droplet while I'm going to rebuild it (because destroy and rebuild are in the same menu). And I lost my IP. Been 5 days trying to get my IP back by creating-destroying droplets, no luck so far. (The result of pinging the IP is still RTO - hoping it's still unassigned to some other droplet)

Floating IPs are not a solution for those of us who need PTR records. They’re also not a solution to the problem of needing to retain existing anchor/permanent IPs. This has been holding up using DO at work. We stick to AWS, in big part, because of this feature. It’s also a personal annoyance.