Zonal VM extension policies Stay organized with collections Save and categorize content based on your preferences.
Preview
This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.
Zonal extension policies let you manage extensions in a single zone within aproject. Each policy specifies extensions that you need to install and a scope,such as VMs in a specific zone or VMs with particular labels.
The following diagram illustrates how you can use zonal extension policies toapply to VMs based on zones and labels:
As shown in the preceding diagram, you can define zonal extension policies atthe project level. These policies apply to VMs in a specific zone that match theselection criteria. For example, in Zone A, extension policyE1 targets VMswith the labelenv=prod to install Extension for SAP, and in Zone B, extensionpolicyE4 targets VMs with no labels to install Extension for Compute Workloadand Ops Agent.
The guest agent on each VM periodically communicates with Google Cloud tocheck for applicable policies. If a VM is targeted by a policy,VM Extension Manager installs the specified extensions and keeps itup-to-date according to the policy. If no extensions are installed on a VM, theguest agent checks for policy updates every eight minutes.If there are extensions installed, it checks every minute.
What's next
To learn more about managing extensions, see the following resources:
- Install VM extensions by creating extension policies
- Manage VM extensions by using extension policies
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.