The network profile resource and an RDMA network profile are available in General Availability

## Feature The network profile resource and an RDMA network profile are available in **General Availability**. You can create a VPC network with the RDMA network profile, which lets you run AI workloads on VM instances that have RDMA network interfaces (NICs). For more information, see the following: * [Network profiles overview](https://cloud.google.com/vpc/docs/network-profiles) * [RDMA network profile](https://cloud.google.com/vpc/docs/rdma-network-profiles) ## Feature If you're a service producer that makes a service available through VPC Network Peering, you can [migrate your service to Private Service Connect](https://cloud.google.com/vpc/docs/about-migrating-peering-services-private-service-connect) without changing the IP address that consumers use to access the service. This feature is available in **Preview**. ## Feature You can create an internal range with the usage type `FOR_MIGRATION` to migrate a CIDR range from one subnet to another. For more information, see [Migrating subnet ranges](https://cloud.google.com/vpc/docs/internal-ranges#for-migration). This feature is available in **General Availability**. ## Feature If you create a Private Service Connect backend to connect to a published service, and the producer has let you know which port the service is available on, you can [include the producer port in the backend configuration](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends#neg-published-service). For more information about the producer's configuration, see [Producer port configuration](https://cloud.google.com/vpc/docs/about-vpc-hosted-services#producer-ports). Specifying the producer port in a Private Service Connect backend is available in **General Availability**.