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 21, 2024
VMware Engine ve1 nodes are now available in the following additional region:
- Dallas, Texas, North America (
us-south1-b).
November 20, 2024
VMware Engine ve2 nodes are now available in the following regions:
- São Paulo, Brazil (
southamerica-east1) - Santiago, Chile (
southamerica-west1)
October 17, 2024
Stretched private clouds using `ve2' node types are now available in the following region:
- Frankfurt, Germany, Europe (
europe-west3)
October 16, 2024
Added missing release notes for stretched private cloud availability using ve2 node types in Sydney, Australia, APAC (australia-southeast1-b)
October 09, 2024
VMware Engine ve2 nodes are available in Frankfurt, Germany, Europe (europe-west3-b).
VMware Engine ve1 nodes are available in Jurong West, Singapore, APAC (asia-southeast1-b).
September 26, 2024
VMware Engine ve2 nodes are available in Frankfurt, Germany, Europe (europe-west3-a).
September 03, 2024
VMware Engine now offers GA support for VPC Service Controls. VPC Service Controls provides an additional layer of security to prevent data exfiltration and unauthorized access. For more information, see VPC Service Controls.
August 09, 2024
VMware Engine ve2-mega-64 node type is generally available in the australia-southeast1 region. For more information on the node type, see Node types. To use the node type in the australia-southeast1 region, contact your Google account team.
August 04, 2024
Stretched Private Clouds using `ve2' node types are now available in the following region:
Sydney, Australia, APAC (australia-southeast1-b)
July 29, 2024
You can now purchase Fully licensed commitments, Fully licensed convertible commitments, and Portable License commitments. For more information, see Purchasing VMware Engine commitments.
July 25, 2024
VMware Engine ve2 nodes are available in the following additional zones:
- Sydney, Australia, APAC (
australia-southeast1-b) - Ashburn, Virginia, North America (
us-east4-b)
July 24, 2024
New VMware Engine ve2 node types are available in the australia-southeast1, us-central1, and us-east4 regions:
HCI node types
ve2-standard-96ve2-mega-96ve2-mega-128
Storage only node types
ve2-standard-sove2-mega-so
See VMware Engine node types for more information on node types.
July 19, 2024
VMware Engine ve2-standard-128 node type is generally available in us-central1 region. For more information on the node type, see Node types. To use the node type in us-central1 region, contact your Google account team.
July 11, 2024
Added missing release notes for ve2-standard-128 availability in australia-southeast1 region
June 14, 2024
VMware Engine ve2-standard-128 node type is generally available in australia-southeast1 region. For more information on the node type, see Node types. To use the node type in australia-southeast1 region, contact your Google account team.
May 24, 2024
When you initiate deletion of a private cloud, billing now stops immediately, but the deletion might take up to 24 hours to complete.
This lets you contact support if you need to stop the deletion. During the deletion of the private cloud, it is still visible in the console, and your VMs continue to run.
If necessary, disable or reconfigure networking components.
May 21, 2024
All new VMware Engine private clouds now deploy with the following:
- VMware vSphere version 7.0 Update 3
- NSX-T version 3.2.3.1
Existing private clouds will be upgraded in May and June 2024.
For more details on the contents of this upgrade, see Service announcements.
April 01, 2024
Storage-only nodes are now generally available. For more information, see Use storage-only nodes.
March 11, 2024
Google Cloud VMware Engine now leverages Cloud Logging to provide status updates about hardware health and VMware management components. The logs are available in Logs Explorer with the following log name:
projects/PROJECT_ID/logs/vmwareengine.googleapis.com%2Falerts
These logs are also available in the Google Cloud VMware Engine UI on the Dashboard in Logs.
March 07, 2024
Beginning mid-March 2024, the VMware Engine operations team will upgrade VMware components to newer versions. 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 Latest service annoucements.
February 28, 2024
Beginning on March 12, 2024, the VMware Engine operations team will perform essential maintenance of the network infrastructure to improve equipment robustness and apply security patches. 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 annoucements.
February 27, 2024
Purchasing commitments for node types is now generally available. For more information, see Purchasing commitments for node types.
February 16, 2024
VMware Engine ve2-standard-128 node type is generally available in us-east4 region. For more information on the node type, see Node types. To use the node type in us-east4 region, contact your Google account team.
December 18, 2023
Google Cloud VMware Engine now supports additional Terraform resources for automating private cloud, cluster, and network management. These enhancements to the VMware Engine Terraform provider enables full environment Infrastructure-as-Code for your VMware Engine Environment. This release includes support for:
- Standard PC (GA Promotion)
- Cluster (GA Promotion)
- Standard VEN support
- Network peering
- Network policy management
- Dns server ip
- Subnet management
- External IP addresses
- Nsx credential management
- Vcenter credential management
- Time limited PC (Single node PC)
To learn more about these new features and how to get started, please visit the VMware Engine documentation on the Hashicorp site and review the IaC Foundations blueprint.
December 12, 2023
Specific Google Cloud VMware Engine resources have been onboarded to Cloud Asset Inventory and Search (CAIS) and are now available through the CloudAsset APIs. This allows you to search, export, and analyze asset metadata associated with the onboarded resources.
The following resources have been onboarded:
- PrivateCloud
- Cluster
- VMwareEngineNetwork
- NetworkPeering
- PrivateConnection
- NetworkPolicy
- ExternalAccessRule
- ExternalAddress
These resources are also available using the global search on the Google Cloud Console and under the Asset Inventory UI.
Learn more about:
- the list of resources available using CAIS and search for VMware.
- what you can do with CAIS.
November 14, 2023
Google Cloud console experience for VMware Engine: You can use the Google Cloud console to manage your VMware Engine environments without opening another tab. For more information on migrating to this refreshed experience, see What's new with VMware Engine.
VMware Engine network: Further simplification of the networking architecture and experience in VMware Engine removes the need for private service networking. With VMware Engine networks, you can create multiple isolated networks within the same project and connect them as needed to consumer VPCs to deliver complex topologies.
Integrated networking: Private cloud deployment is now just one simple step. VMware Engine network and initial VPC peering to your VPC can be done at the time of private cloud creation.
Advanced VPC Peering: Virtual Private Cloud network peerings define network connectivity between VMware Engine networks, Google VPCs, and other services. You can now create a complex set of VPC peerings within the Google Cloud console.
Increase to the default VPC Peer count: Any standard VMware Engine network now supports 25 VPC Peers by default.
Integrated Cloud DNS for workloads (DNS Bindings): Bi-directional Cloud DNS capabilities that enable DNS resolution for VMware Engine workloads, delivering enterprise needs in a simplified and more streamlined manner. Cloud DNS administrators can bind the VMware Engine network just as any other VPC.
DNS Server IP: Workloads within your private cloud can now use native Cloud DNS for DNS resolution.
Management DNS for private clouds: Automatic Management DNS Peering is now Automatic Management DNS for Private Clouds. You can now view and manage the DNS bindings for the private cloud management zone.
External access rules: Control access to external IP addresses. We have simplified the rule creation process to no longer require creation of a table and attachment to a subnet. External access rules now support one or more external IP address within a single rule.
(Legacy Networks) DNS forwarding rules: Allows configuration of management appliance DNS resolution for private clouds attached to legacy VMware Engine networks.
ESXi (NSX-T Distributed Log Forwarding): You can now configure both ESXi logs, including NSX-T Distributed Firewall (DFW) Logs, to a remote syslog server.
Finer-grained access controls for additional resources: VMware Engine provides finer-grained, per-action access controls for actions performed on new resources added. To view a comprehensive list of permissions for VMware Engine, go to the Permissions reference and search for the prefix vmwareengine.
Additional Google Cloud CLI and VMware Engine API Endpoints: More capabilities delivered using VMware Engine API and Google Cloud CLI enables you to programmatically manage VMware Engine environments, including VMware Engine API and Google Cloud CLI functions for managing the new networking model, network peering, external access rules and external IP service, consumer DNS, and more.
DNS Profiles: Existing DNS Profiles will be migrated to each private cloud in which the DNS Profile was assigned. DNS forwarding rules can be configured within each private cloud.
Firewall Tables: Existing firewall tables and rules have been migrated to external access rules.
Elevate privilege option is no longer available. You can sign in using one of the solution users to perform elevated privileges actions. For details, see Elevating VMware Engine privileges.
Announced August 10, 2022: Removed ability to manage point-to-site (P2S) VPN gateways for projects with existing P2S VPN gateways. You can continue to use an alternative VPN solution. For details, see Connecting using VPN. Contact customer care for P2S VPN gateway removal.
September 30, 2023
VMware Engine nodes are now available in the following additional zone:
- Tel Aviv (
me-west1-b)
September 13, 2023
VMware Engine nodes are now available in the following additional zone:
- Tel Aviv (
me-west1-a)
June 28, 2023
Google Cloud VMware Engine now supports ESXi syslog forwarding, including distributed firewall logs, which provides more visibility into security events on VMware Engine instances.
Enhanced Service Controls: VMware Engine is also releasing additional security controls that will enable you to manage permissions elevation. This enhanced security model gives you more granular control over how Google support staff access your VMware Engine instances for workloads that require additional controls due to regulatory or compliance reasons. Please contact support for assistance with configuring these services.
Google Cloud VMware Engine now supports Terraform for private cloud, cluster, and network management. This release covers Create, Update, and Delete commands for private cloud resources. The VMware Engine Terraform provider enables Infrastructure-as-Code for your VMware Engine Environment.
To learn more about these new features and how to get started, please visit the VMware Engine documentation on the Hashicorp site and review the IaC Foundations blueprint.
June 26, 2023
Pay-as-you-go (PAYG) licenses for Windows Server are now available in Preview.
June 21, 2023
Stretched Private Clouds are now available in the following region:
- London, England, Europe (
europe-west2)
Stretched Private Clouds allow you to stretch your vSphere/vSAN clusters across Google Cloud zones and protect against zone-level failures. This functionality enables high levels of availability for business critical applications.
June 14, 2023
Google Cloud VMware Engine now supports the provisioning of Single Node Private Clouds, configuration of Management Subnets (HCX and Service Subnets), as well as CRUD of Private Connections using the GCloud CLI and VMware Engine API. These features streamline your VMware Engine process flows by using higher degrees of automation.
May 25, 2023
VMware Engine nodes are now available in the following additional region:
- Turin, Italy (
europe-west12)
May 16, 2023
VMware Aria Operations for Logs is now certified for Google Cloud VMware Engine. You can use VMware Aria Operations for Logs to collect and manage logs from VMware Engine and on-prem environments into a centralized solution.
VMware Aria Operations for Logs with VMware Engine enables more operational visibility and intelligent analytics for both troubleshooting and auditing purposes, making it easier for you to manage and operate your VMware Engine environment. See the VMware blog announcement for more information.
May 02, 2023
After installing Windows Server 2022 update KB5022842 (OS Build 20348.1547), guest OS can not boot up when virtual machine(s) is configured with secure boot enabled. For more information, see Virtual Machine with Windows Server 2022 KB5022842 (OS Build 20348.1547) configured with secure boot enabled not booting up. To work around this issue, you can do one of the following:
- Skip KB5022842 and use KB5023705
- Disable "Secure Boot" on affected VMs
April 25, 2023
VMware Engine adds a VPC Service Controls guided opt-in and policy export that enables you to attach VMware Engine services to a new or existing VPC Service Controls perimeter. For more information, see VPC Service Controls.
March 31, 2023
VMware Engine nodes are now available in the following additional region:
- Santiago (
southamerica-west1)
VMware Engine nodes are now available in the following additional zone:
- London, England (
europe-west2-b)
March 14, 2023
Resource name translation will be required after April 2023.
For more information on resource name translation, see Resource Name Translation.
March 09, 2023
VMware Engine nodes are now available in the following additional region:
- Delhi (
asia-south2)
February 22, 2023
VMware Engine private clouds support the addition of a Trusted Platform Module (TPM) 2.0 virtual cryptoprocessor to a virtual machine.
For details about this feature, see About Virtual Trusted Platform Module.
January 23, 2023
Removed ability to create stateful outbound firewall rules for new projects and projects that have not yet created stateful outbound rules. Customers can continue to create a firewall rule set in NSX-T Gateway or NSX-T Distributed Firewall rules to limit or control outbound access.
January 17, 2023
If you are running VMware Engine Horizon (VDI) on Google Cloud VMware Engine, you may encounter errors after changing your private cloud resource naming to meet the standards for Google Cloud CLI and VMware Engine API.
To troubleshoot this issue, see VMware Engine Known issues.
January 13, 2023
Stretched private clouds are now available in the australia-southeast1 (Sydney) Google Cloud region. Stretched private clouds enable you to stretch your vSphere/vSAN clusters across Google Cloud zones and protect against zone level failures. This functionality enables high levels of availability for business critical applications.
December 21, 2022
VMware Engine nodes are now available in the following additional region:
- Milan, Italy, Europe (
europe-west8)
December 08, 2022
In order to support new features in the future, Google Cloud VMware Engine will convert the resource names for private clouds to a standardized format that is more consistent with Google Cloud. Specifically, this resource name translation will make minor changes to the names of resources in your project, such as:
- Changing capital letters to lowercase
- Changing white space to hyphens
Resource name translation is currently optional, but existing private clouds must perform a resource name translation in order to access the gcloud CLI or VMware Engine API. Resource name translation will be required after September 2023.
For more information on resource name translation, see Resource Name Translation.
November 28, 2022
Zerto Solution version 9.5u1 is now supported as a disaster recovery solution with VMware Engine. Learn more about setting up Zerto Solution.
Preview: VMware Engine private clouds support the addition of a Trusted Platform Module (TPM) 2.0 virtual cryptoprocessor to a virtual machine.
For details about this feature, see About Virtual Trusted Platform Module.
November 17, 2022
Starting November 17, 2022, newly created private clouds will utilize IP address layout (IP Plan) version 2.0 subnet allocations. HCX addressing is now included in the management CIDR allocation, simplifying the process of starting data center VM migrations. IP Plan version 2.0 also enables additional scale and features delivered to your public cloud in upcoming releases.
Stretched private clouds are now available in the europe-west3 (Frankfurt) region. You can use stretched private clouds to stretch vSphere/vSAN clusters across zones and protect against zone level failures. This functionality enables high levels of availability for business critical applications.
You can now use the gcloud command-line tool or the API to manage VMWare Engine networks, network policies, and private clouds. See the API reference or the gcloud SDK for more information.
October 06, 2022
VMware Engine adds five service subnets for newly created private clouds. Service subnets are used for appliance or service deployment scenarios, such as storage, backup, Site Recovery Manager (SRM), disaster recovery (DR), media streaming, and providing high scale linear throughput and packet processing for private clouds at any scale.
See Subnets for more information on service subnets.
September 23, 2022
Dell PowerScale is now available for in-guest file share access for Google Cloud VMWare Engine VMs:
- NFS and SMB shares supported
- PowerScale file shares may be accessed across Google Cloud VMWare Engine and other Google Cloud services
- Private connection configured via the VMware Engine UI
Learn more about PowerScale for Google Cloud VMWare Engine.
August 10, 2022
Removed ability to create stateless firewall rules for new projects and projects that have not yet created stateless rules. Projects containing existing stateless rules can continue to modify those rules. Customers can continue to create a firewall rule set in NSX-T Gateway or NSX-T Distributed Firewall rules.
In March 2023, we plan to remove any remaining stateless rules that have not been transitioned to NSX-T Gateway or NSX-T Distributed Firewall rules. If there are any questions about how to make this transition, contact Cloud Customer Care.
Removed ability to create point-to-site (P2S) VPN gateways for new projects and projects that have not yet created P2S VPN gateways. Projects containing existing gateways can continue to modify those gateways. Customers can continue to use an alternative VPN solution. For details, see Point-to-site VPN gateways.
In March 2023, we plan to remove any remaining VPN gateways that have not been transitioned to an alternative VPN solution. If there are any questions about how to make this transition, contact Cloud Customer Care.
July 27, 2022
Resource creation of named objects now enforce naming requirements that match other Google Cloud products like Compute Engine. New resources must use names that are 1-63 characters long, comply with RFC 1035, and consist of lowercase letters, digits, and hyphens. For example, "privatecloud-123".
July 13, 2022
VMware Engine nodes are now available in the following additional region:
- Zurich, Switzerland, Europe (
europe-west6)
May 31, 2022
Private cloud creation now uses the HCX Enterprise license level by default, enabling the following premium HCX features:
- HCX Replication Assisted vMotion (bulk, no-downtime migration)
- Migrations from KVM and Hyper-V to vSphere
- Traffic engineering
- Mobility groups
- Mobility-optimized networking
For more information about private cloud VMware components, see Private cloud VMware components.
May 20, 2022
Beginning on May 30 2022, the VMware Engine operations team will continue performing essential maintenance of the network infrastructure to improve equipment robustness and apply security patches. 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.
April 29, 2022
The VMware Engine operations team will apply important security updates to vCenter Server and NSX-T beginning early May 2022. Users affected by this upgrade will receive an email with planned maintenance dates and times.
For details about the maintenance scope and impact, see Service announcements.
April 04, 2022
VMware Engine nodes are now available in the following additional zone:
- Ashburn, Northern Virginia, North America (
us-east4-b)
March 25, 2022
Added ability to set the number of cores available per node in a cluster to meet your application-specific requirements during cluster creation. When you use a custom core count, any future expansions or maintenance of that cluster will also use the custom core count.
The public IP service now supports the ICMP protocol, and default firewall rules for new projects expand the previous outbound rule to allow outbound TCP, UDP, and ICMP any.
Users with Google Cloud projects created before March 8, 2022 must contact Cloud Customer Care to enable the allow-icmp-to-internet firewall rule.
February 15, 2022
Beginning on February 21 2022, the VMware Engine operations team will perform essential maintenance of the network infrastructure to improve equipment robustness and apply security patches. 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.
December 28, 2021
VMware Engine nodes are now available in the following additional region:
- Toronto, Ontario, North America (
northamerica-northeast2)
VMware Engine nodes are now available in the following additional zone:
- Sydney, Australia, APAC (
australia-southeast1-b)
December 15, 2021
Added ability to forward syslog messages of a desired severity (like Error or Warning) to Cloud Logging from NSX-T. You can set up alerts and dashboards based on those messages in Google Cloud's operations suite.
For details about this feature, see Configure a private cloud for syslog forwarding.
November 30, 2021
The process of allocating an external IP address for an internal workload VM now includes the private cloud field. This field is visible when viewing IP address details and logically associates the external IP address to the private cloud that contains the workload VM.
Added ability to create private clouds that contain a single node for testing and proofs of concept with VMware Engine.
Note that VMware Engine deletes private clouds that contain only 1 node after 60 days, and a private cloud must contain at least 3 nodes to be eligible for coverage based on the SLA.
November 22, 2021
Added an update to the September 22, 2021 service announcement. Continuing in December 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.
As of November 4, 2021, Google Cloud VMware Engine achieves the following compliance certifications:
November 10, 2021
VMware Engine nodes are now available in the following additional zone:
- Frankfurt, Germany:
europe-west3-b
October 29, 2021
Generally available: 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.
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.