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 page, browse and filter all release notes in the Google Cloud Console, or you can 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: https://cloud.google.com/feeds/vmware-engine-release-notes.xml

October 13, 2021

All new VMware Engine private clouds now deploy with VMware vSphere version 7.0 Update 2 and NSX-T version 3.1.2. Existing private clouds will be upgraded to vSphere version 7.0 Update 2 and NSX-T version 3.1.2 over a period of time in October 2021.

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

Generally available: vSAN data encryption for data at rest now uses keys generated by Cloud Key Management Service for all new private clouds.

For details about this feature, see About vSAN encryption.

September 22, 2021

Beginning in the middle of October 2021, VMware Engine will upgrade the VMware stack from version 7.0 Update 1 to 7.0 Update 2 and the NSX-T stack from version 3.0 to 3.1.2. 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.

September 21, 2021

Added security bulletin for the VMware Engine response to VMware security advisory VMSA-2021-0020.

August 20, 2021

Preview: VMware Engine integration with Google Cloud's operations suite using a standalone metrics and logs agent. The agent brings syslog messages and metrics from vCenter and vSAN to Google Cloud's operations suite, where you can set up your own dynamic alerts on over 50 metrics and leverage pre-built dashboards.

For details about this feature, see Setting up Cloud Monitoring with a standalone agent.

July 14, 2021

Changed MTU recommendation for private cloud-to-private cloud external communications to 1500 bytes.

June 17, 2021

Added autoscale policies that can automatically expand or shrink a cluster in your private cloud based on factors like CPU utilization or storage capacity thresholds. All clusters begin with a default autoscale policy that adds a node based on a storage capacity threshold.

For details about this feature, see Autoscale policies.

Preview: vSAN data encryption for data at rest now uses keys generated by Cloud Key Management Service for all new private clouds.

For details about this feature, see Configuring vSAN encryption for your private cloud.

Removed vCenter privilege Host > Configuration > Storage partition configuration for role Cloud-Owner-Global-Role. This prevents the mounting of iSCS or NFS storage as a datastore on your private cloud vSphere cluster. If you have any iSCSI or NFS datastore mounted on your private cloud cluster, contact Cloud Customer Care.

Enabled TRIM/UNMAP support on vSAN at the time of private cloud creation for more efficient vSAN storage by default. To enable this feature on existing workload VMs, you must reboot the VMs.

Added the following vCenter privileges to the Cloud-Owner-Global-Role role:

  • Guest operation alias modification
  • Guest operation alias query
  • Guest operation modifications
  • Guest operation program execution
  • Guest operation queries

Added vSphere content library management privileges to the Cloud-Global-VM-admin-group group. With this change, a VM admin can add, delete, and read content library items.

The Quotas page in the Cloud Console no longer shows VMware Engine node usage as 0 when you have an active private cloud.

May 25, 2021

Added security bulletin for the VMware Engine response to VMware security advisory VMSA-2021-0010.

May 17, 2021

VMware Engine nodes are now available in the following additional region:

  • Mumbai, India, APAC (asia-south1)

April 09, 2021

Added global quota limits for VMware Engine nodes so users have more flexibility in distributing resources across regions.

For details, see Quotas and limits.

Updated the display name of VMware Engine quota entries to reflect the resource type and assignment level. Quotas available to assign for VMware Engine are as follows:

  • VMware Engine standard 72 vCPUs nodes across regions
  • VMware Engine standard 72 vCPUs nodes per region

April 01, 2021

The Google Cloud Business Associate Agreement (BAA) now also covers Google Cloud VMware Engine. Businesses in the healthcare vertical who need HIPAA compliance can run their workloads on Google Cloud VMware Engine.

For details, see HIPAA Compliance on Google Cloud Platform.

Restructured documentation to better group content and improve workflow discoverability.

March 25, 2021

Added support for using NetApp Cloud Volumes Service for Google Cloud. You can use cloud volumes as NFS mount points or SMB shares in your workload virtual machines.

For details, see Connecting workload VMs to NetApp Cloud Volumes Service.

March 17, 2021

VMware Engine nodes are now available in the following additional region:

  • Council Bluffs, Iowa, North America (us-central1)

March 05, 2021

Added security bulletin for the VMware Engine response to VMware security advisory VMSA-2021-0002.

February 19, 2021

Added upfront prepay option for 3-year and 1-year commitment contracts. VMware Engine provides an option to unlock up to 50% off the hourly rate savings on resources through the prepay upfront option. Contact Sales for more information.

February 17, 2021

Added password management of the CloudOwner@gve.local user for vCenter and the admin user for NSX-T Manager. VMware Engine generates a password for these users when you deploy a private cloud. You can view and reset credentials from the private cloud details page.

Added the ability to peer multiple VPCs with private clouds in a region. This improvement enables you to establish a many-to-many relationship between your VPCs and regions.

Added support for global DNS name resolution for management components of your private cloud using Cloud DNS. You can set up Cloud DNS to resolve domain names of management components of multiple private clouds (in the same or different regions) in your project.

For more information, see Configuring DNS for vCenter access.

Updated private cloud nodes so that the ESXi advanced parameter fakescsireservation and MAC learning are now enabled by default. This allows creation of a nested ESXi environment on your private cloud.

Added missing release notes for previous region launches of VMware Engine resources:

  • Montréal, Québec (northamerica-northeast1)
  • São Paulo, Brazil (southamerica-east1)
  • Jurong West, Singapore (asia-southeast1)
  • Eemshaven, Netherlands (europe-west4)
  • Sydney, Australia (australia-southeast1)
  • London, England (europe-west2)
  • Tokyo, Japan (asia-northeast1)
  • Frankfurt, Germany (europe-west3)

January 22, 2021

VMware Engine nodes are now available in the following additional region:

  • Montréal, Québec (northamerica-northeast1)

December 27, 2020

VMware Engine nodes are now available in the following additional region:

  • Osasco, São Paulo, Brazil (southamerica-east1)

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.

November 20, 2020

VMware Engine nodes are now available in the following additional region:

  • Jurong West, Singapore (asia-southeast1)

October 30, 2020

VMware Engine nodes are now available in the following additional region:

  • Eemshaven, Netherlands (europe-west4)

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.

October 06, 2020

VMware Engine nodes are now available in the following additional region:

  • Sydney, Australia (australia-southeast1)

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.

August 31, 2020

VMware Engine nodes are now available in the following additional region:

  • London, England, Europe (europe-west2)

August 24, 2020

VMware Engine nodes are now available in the following additional region:

  • Tokyo, Japan (asia-northeast1)

August 20, 2020

VMware Engine nodes are now available in the following additional region:

  • Frankfurt, Germany Europe (europe-west3).

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.