VMware Engine is upgrading existing private clouds to use newer VMware components. See Service announcements for more details.

Release notes

This page documents production updates to Google Cloud VMware Engine. Check this page for announcements about new or updated features, bug fixes, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud release notes page.

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: https://cloud.google.com/feeds/vmware-engine-release-notes.xml

December 14, 2020

All new VMware Engine private clouds now deploy with VMware vSphere version 7.0 and NSX-T version 3.0. Existing private clouds will be upgraded to vSphere version 7.0 and NSX-T version 3.0 over a period of time in December 2020 and January 2021.

See Service announcements for more details on the contents of this upgrade.

Increased maximum number of nodes in a private cloud cluster to 32. This change applies to new clusters. Existing clusters can be expanded up to 32 nodes after the upgrade to vSphere 7.0 version.

When VMware Engine replaces a failed node, node customizations now transfer from the failed node to the replacement node. Customizations include vSphere labels, vSphere custom attributes, vSphere tags, and any affinity and anti-affinity rules.

VMware Engine now advertises routes learned from a VPC to your VMware Engine private cloud network, and advertises routes learned from your private cloud to a VPC. This allows network communication between Google Cloud resources and private cloud resources.

November 23, 2020

Beginning in the middle of December 2020, VMware Engine will upgrade the VMware stack from version 6.7 to 7.0 and the NSX-T stack from version 2.5 to 3.0. Users affected by this upgrade will receive an email with planned maintenance dates and times.

For details about the upgrade and steps to prepare, see Service announcements.

October 12, 2020

Multi-region private cloud to private cloud connectivity is now available. Private clouds of your project in different regions can automatically route traffic between them. No additional connectivity is required to enable this routing.

Enabled HCX private cloud to private cloud migration. You can now use HCX to migrate VMs between two private clouds.

End-to-end dynamic routing is now available between on-premises networks and VMware Engine regions. With this feature, your VMware Engine private clouds can learn custom or reserved-block Public IP (non RFC-1918) range networks in your VPC or on-premises dynamically.

RFC 6598 (non-private) address range support for management and workload networks is now available. With this release, you can specify non-private address ranges for management and workload networks when you create your private cloud. Those addresses will then be included for any route exchange with VPC and on-premises networks.

September 28, 2020

Committed use discounts (CUDs) are available to purchase for Google Cloud VMware Engine. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With spend-based committed use discounts for VMware Engine, you can earn a deep discount off your cost of use in exchange for committing to continuously use VMware Engine nodes in a particular region for a 1- or 3-year term. See the documentation for more details.

June 30, 2020

Google Cloud VMware Engine is generally available. This service delivers a fully managed VMware platform stack—VMware ESXi, vCenter, vSAN, NSX-T, and HCX—in a dedicated environment on Google Cloud's infrastructure to support your enterprise production workloads. Using VMware Engine, you can bring your on-premises workloads to Google Cloud by connecting to a dedicated VMware environment.

You can run the service in the us-east4 (Ashburn, Northern Virginia) and us-west2 (Los Angeles, California) regions.

For more information, read the VMware Engine documentation.