This page describes how to remove a private services access allocated range that you have been using for an AlloyDB.
When you create an AlloyDB cluster or instance in a region that doesn't yet have any clusters or instances, AlloyDB creates a subnet in that region in a Google-owned and managed project, which is called a tenant project. The subnet is connected to your network using the private service connection VPC Network Peering.
If you decide to remove all an AlloyDB resources associated with an allocated range, as well as the allocated range, follow the steps in this document to ensure that your network resources are cleaned up.
Before you begin
- The Google Cloud project you are using must have been enabled to access AlloyDB.
- You must have one of these IAM roles in the Google Cloud project you are using:
roles/alloydb.admin(the AlloyDB Admin predefined IAM role)roles/owner(the Owner basic IAM role)roles/editor(the Editor basic IAM role)
If you don't have any of these roles, contact your Organization Administrator to request access.
- To increase the IP address range, you also must have these IAM
permissions:
compute.networks.listcompute.addresses.createcompute.addresses.listservicenetworking.services.addPeering
Remove an allocated range
To remove an allocated range associated with your an AlloyDB resources, follow these steps:
- Delete all AlloyDB resources that are using the allocated range.
- Remove the allocated range from the private service connection.
- Delete the allocated range.
- Contact Support and ask them to delete the subnets that private services access created on the tenant project.