This page documents production updates to Network Connectivity Center and Router appliance. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.
You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
November 20, 2024
Route exchange with VPC spokes is now generally available.
This feature lets you lets you connect VPC spokes and hybrid spokes, such as Cloud Interconnect VLAN attachments, HA VPN tunnels, and Router appliance VMs on the same hub.
Note that billing for Advanced Data Networking (ADN) fee for traffic originating from Google Cloud Platform egressing through hybrid spokes starts in Dec, 2024.
October 03, 2024
Producer VPC Spokes is now available in public preview.
If you have a VPC network that consumes a service offered through private services access, you can use a Network Connectivity Center producer VPC spoke to make the service reachable by other spokes on a hub.
August 30, 2024
Preset topologies and include export filters are generally available.
Preset topologies let you specify the connectivity configuration across all VPC spokes. You can choose between mesh or star preset topologies. Include export filters lets you limit connectivity by specifying a list of permitted CIDR ranges, thereby blocking all but the permitted IP address ranges.
June 27, 2024
Route exchange with VPC spokes is now available in public preview.
This feature lets you lets you connect VPC spokes and hybrid spokes, such as Cloud Interconnect VLAN attachments, HA VPN tunnels, and Router appliance VMs on the same hub.
June 20, 2024
Include export filters is now available in public preview.
This feature lets you limit connectivity by specifying a list of permitted CIDR ranges, thereby blocking all but the permitted IP address ranges.
June 14, 2024
Private Service Connect connection propagation is now available in public preview.
The propagation of Private Service Connect services through the Network Connectivity Center hub enables VPC-hosted services in private VPC networks to be reachable across VPC networks.
May 29, 2024
Preset topologies are now available in public preview. Network Connectivity Center lets you specify connectivity configuration across all VPC spokes.
November 16, 2023
The Advanced Data Networking (ADN) traffic is accounted only for large-sized flows (approximately >20 Kbps) that cross VPC boundaries. Currently, small-sized flows are not accounted.
November 08, 2023
Connecting VPC networks by using Network Connectivity Center is now generally available.
This feature lets you connect two or more VPC networks, represented as spokes, to a hub in the same or a different project for full mesh connectivity.
September 19, 2023
The issue that you cannot get the status of a long-running operation for a spoke without the networkconnectivity.operations.get IAM permission in the spoke project is now resolved.
The new API and gcloud commands are documented on the Review proposed VPC spokes page. The previous API methods and gcloud commands are now deprecated.
August 08, 2023
The AcceptSpoke and RejectSpoke API methods and the network-connectivity spokes accept and network-connectivity spokes reject CLI commands have the following usability issue:
- As the user, if you do not have the
networkconnectivity.operations.getIAM permission in a spoke project, you cannot get the status of a long-running operation for that spoke.
The issue is being worked on. The workaround is that the spoke administrator can grant the required permissions to the appropriate hub administrator. For information about granting permissions, see Give access.
July 12, 2023
Connecting VPC networks by using Network Connectivity Center is now available in Preview.
This feature lets you connect two or more VPC networks, represented as spokes, to a hub in the same or a different project for full mesh connectivity.
May 31, 2023
Cross-Cloud Interconnect is now generally available. You can use a Cross-Cloud Interconnect connection to peer your Google Virtual Private Cloud (VPC) network with your network that's hosted by a supported cloud service provider. You can also use Cross-Cloud Interconnect VLAN attachments as part of a site-to-site data transfer strategy.
For example, after you configure a VLAN attachment for your Cross-Cloud Interconnect connection, you can create a Network Connectivity Center spoke to represent the attachment. If the spoke has site-to-site data transfer enabled, you can then transfer data between your remote cloud network and your other external sites. Other external sites can include your on-premises network or your network in other clouds.
For information about the cloud service providers that Cross-Cloud Interconnect supports, see the Cross-Cloud Interconnect overview. For information about site-to-site data transfer, see the Site-to-site data transfer overview.
Site-to-site data transfer is supported only in certain locations.
November 09, 2022
The Google Cloud console now lets you do all of the following:
- See a list of existing hubs
- Create multiple hubs
- Edit an existing hub's description and/or labels
Previously, you could complete these actions only by using the Google Cloud CLI or the API.
Also, the Network Connectivity Center Quotas page has been updated to describe the limit of 60 hubs per project.
For more information about creating and managing hubs, see Work with hubs and spokes.
February 23, 2022
Networking Connectivity Center now supports the use of a third-party network virtual appliance in any Google Cloud region for the following use cases:
- Providing site-to-cloud connectivity
- Providing connectivity or managing traffic between VPC networks
A third-party network virtual appliance could be an SD-WAN router, a firewall appliance, a load balancer, or another appliance, as long as it uses BGP. After you create a Network Connectivity Center spoke to represent your router appliance instance, it can exchange routes dynamically with Cloud Router.
To view a list of partners whose solutions are integrated with Network Connectivity Center, see Network Connectivity Center partners.
For more information about Network Connectivity Center, see the product overview.
October 26, 2021
The issue reported on Sept. 30, 2021, has been resolved. Cloud DNS forwarding services and Private Google Access can now be accessed through Router appliance spokes.
October 18, 2021
Network Connectivity Center is now generally available. For more information, see the Network Connectivity Center overview.
It is now possible to add or remove router appliance instances from an existing spoke, as long as you don't try to add instances that belong to a different VPC network. For details, see Working with hubs and spokes.
September 30, 2021
Cloud DNS forwarding services and Private Google Access cannot be accessed through Router appliance spokes. This issue is being worked on.
September 29, 2021
Previously, if you used a Router appliance spoke to connect more than 1,000 VMs, you might have experienced problems establishing BGP sessions between the router appliance instance and the Cloud Router. This issue has been resolved.
Network Connectivity Center includes new limits on the number of underlying resources that can be associated with a spoke. For information about the new limits, see Network Connectivity Center quotas and limits.
September 07, 2021
Previously, if you used a Router appliance spoke to connect more than 1,000 VMs, you might have experienced problems establishing BGP sessions between the router appliance instance and the Cloud Router. This issue has been resolved.
September 02, 2021
You can now create Router appliance spokes by using the Google Cloud Console. For more information, see Working with hubs and spokes.
August 23, 2021
The Spoke Admin role now includes the following permissions:
networkconnectivity.hubs.getnetworkconnectivity.hubs.list
For full details about Network Connectivity Center permissions, see Access control.
July 20, 2021
Network Connectivity Center now supports VPC Service Controls. For details, see Protecting resources with VPC Service Controls.
July 09, 2021
Network Connectivity Center now includes hard limits on the number of resources that can be linked to an individual spoke. For details, see Quotas and limits.
June 28, 2021
It's no longer possible to add or remove router appliance instances to or from an existing spoke. Instead, you must delete and re-create the spoke to include the router appliance instances that you want the spoke to contain. This issue is being worked on.
June 11, 2021
If you use a Router appliance spoke to connect more than 1,000 VMs, you might be unable to establish BGP sessions between the router appliance instance and Cloud Router. The 1,000-VM limit includes any VMs that are accessible through VPC Network Peering.
May 26, 2021
The Cloud documentation now includes a list of partners whose solutions are integrated with Network Connectivity Center.
May 25, 2021
You can now use the Cloud Console to create hubs and spokes in Network Connectivity Center.
March 09, 2021
Router appliance for Network Connectivity Center is available in Preview.
January 25, 2021
Network Connectivity Center is now available in Preview.
For more information, see the Network Connectivity Center overview.