Google Cloud's Terms of Service (section 7) define the
deprecation policy that applies to Cloud VPN. The
deprecation policy only applies to the features or
services listed therein.
After a Cloud VPN feature has been officially deprecated, the feature
continues to be available for at least the period of time defined in the
Terms of Service. After this period of time, the feature or service
will be scheduled for limited support.
The following table lists current Cloud VPN feature deprecations and
their schedules.
| Feature (status) |
Deprecation date |
Details |
| Classic VPN |
March 31, 2022 |
-
You can't create Classic VPN tunnels that use
dynamic routing (BGP) that is managed by a Cloud Router for
connections outside of Google Cloud.
-
You can continue to create Classic VPN tunnels
that use dynamic routing if the Classic VPN connects
to VPN gateway software running inside a Compute Engine virtual
machine (VM) instance.
This configuration is still supported.
|
| Classic VPN |
August 1, 2025 |
-
You can't create Classic VPN
tunnels that use dynamic routing (BGP), regardless of the gateway
the tunnel connects to. This includes connections to
VPN gateway software running inside a Compute Engine VM
instance or connections outside of Google Cloud.
After August 1, 2025, existing tunnels with these configurations
will no longer be supported. Tunnels that are in use will continue
to function, but without an availability SLA.
-
If you delete a tunnel configuration, you won't be able to recreate
it. However, you will still be able to route traffic through your
existing Classic VPN tunnels, unless you make changes
that require you to switch to HA VPN.
For more information, see
Classic VPN dynamic routing deprecation.
|
