Proposal: Process Improvement for Floating IP Confirmation During VSI Deprovisioning

Background

In IBM Cloud’s Virtual Private Cloud (VPC) environment, a Floating IP is typically used to enable external access to a Virtual Server Instance (VSI).
Since Floating IPs can be detached and reused across multiple resources, they provide flexibility and efficient IP utilization.

However, when a VSI is no longer needed and the resource is deleted, the deletion workflow does not include any step or reminder related to the associated Floating IPs.
As a result, users may unintentionally leave Floating IPs allocated, leading to continued billing for unused IP addresses.

Current Issue
• The VSI deletion process does not prompt users to verify or release Floating IPs.
• Floating IPs that are in an “unbound” state (i.e., not attached to any device) may remain allocated and continue to incur charges.
• This leads to unnecessary ongoing costs and resource inefficiency.

Proposed Improvements

I propose the following enhancements to help users manage Floating IPs more effectively during VSI deprovisioning:
Ex. Display an Alert Message During VSI Deletion

When a VSI with an associated Floating IP is deleted, display a message such as:

“A Floating IP previously associated with this VSI may still exist. Please review and delete it if it is no longer needed.”