<?xml version="1.0" encoding="UTF-8"?>

<!-- AUTOGENERATED FILE. DO NOT EDIT. -->

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>tag:google.com,2016:compute-engine-release-notes</id>
  <title>Compute Engine - Release Notes</title>
  <link rel="self" href="https://docs.cloud.google.com/feeds/compute-engine-release-notes.xml"/>
  <author>
    <name>Google Cloud</name>
  </author>
  <updated>2020-04-23T21:59:06.719027+00:00</updated>


  <entry>
    <title>April 20, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april202020</id>
    <updated>2020-04-20T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april202020"/>
    <content type="html"><![CDATA[<ul><li>The <code dir="ltr" translate="no">us-west4</code> Las Vegas, Nevada region is now available to all projects and users. The zones in the <code dir="ltr" translate="no">us-west4</code> region have <a href="https://cloud.google.com/compute/docs/machine-types">N1 and E2 machine types</a>. See <a href="https://cloud.google.com/compute/docs/regions-zones">Regions and zones</a> for more information.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 16, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april162020</id>
    <updated>2020-04-16T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april162020"/>
    <content type="html"><![CDATA[<ul><li>Committed use discount shared billing is now available in <strong>beta</strong>. You can share committed use discounts among all your projects that fall under the same billing account. For more information, see <a href="https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts">Signing up committed use discounts</a>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 15, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april152020</id>
    <updated>2020-04-15T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april152020"/>
    <content type="html"><![CDATA[<ul><li>You can identify VM instances that are not being used with <a href="https://cloud.google.com/compute/docs/instances/viewing-and-applying-idle-vm-recommendations">idle VM recommendations</a>. Use these recommendations to reduce unused resources and reduce your compute bill. This feature is <strong>Generally available</strong>.</li>
<li><p>You can manage, maintain, and view patch compliance for your VM instances using the OS patch management feature. For more information, see <a href="https://cloud.google.com/compute/docs/os-patch-management">OS patch management</a>. This feature is now <strong>Generally available</strong>.</p> <p>The latest stable version of the OS Config agent is <a href="https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20200402.01"><code dir="ltr" translate="no">20200402.01</code></a>. If you were using OS patch management in Beta, you can update the agent on your existing VMs, see <a href="https://cloud.google.com/compute/docs/manage-os#update-agent">Updating the OS Config agent</a>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 09, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april092020</id>
    <updated>2020-04-09T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april092020"/>
    <content type="html"><![CDATA[<ul><li><strong>GA:</strong> <a href="https://cloud.google.com/compute/docs/instances/modifying-shielded-vm">Compute Engine enables Shielded VM features by default</a>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 08, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april082020</id>
    <updated>2020-04-08T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april082020"/>
    <content type="html"><![CDATA[<ul><li>You can identify idle persistent disk resources by using <a href="https://cloud.google.com/compute/docs/disks/viewing-and-applying-idle-pd-recommendations">idle persistent disk recommendations</a>. Following these recommendations will help reduce unused resources and reduce your compute bill. This feature is in <strong>Beta</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 06, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april062020</id>
    <updated>2020-04-06T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april062020"/>
    <content type="html"><![CDATA[<ul><li><p>C2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Ashburn, Northern Virginia, USA <code dir="ltr" translate="no">us-east4-b,c</code></li></ul></li>
<li><p>N2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>The Dalles, Oregon, USA <code dir="ltr" translate="no">us-west1-b</code></li>
<li>Ashburn, Northern Virginia, USA <code dir="ltr" translate="no">us-east4-a</code></li>
<li>St. Ghislain, Belgium <code dir="ltr" translate="no">europe-west1-d</code></li></ul></li>
<li><p><a href="https://cloud.google.com/compute/docs/machine-types#n2d_machine_types">N2D machine types</a> are now <strong>Generally Available</strong>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>April 01, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#april012020</id>
    <updated>2020-04-01T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#april012020"/>
    <content type="html"><![CDATA[<ul><li><p>You can now define where your VM instances are located relative to each other on the underlying host systems in a Google datacenter. Create a placement policy to locate VM instances close to each other for low latency, or create a policy to spread VM instances out so that they do not share the same infrastructure. See <a href="https://cloud.google.com/compute/docs/instances/define-instance-placement">Defining instance location within a zone</a> to learn more.</p></li>
<li><p>NVIDIA® Tesla® T4 GPUs are now available in the following additional regions and zones:</p> <ul><li>Frankfurt, Germany: <code dir="ltr" translate="no">europe-west3-b</code></li></ul> <p>For information about using T4 GPUs on Compute Engine, see <a href="https://cloud.google.com/compute/docs/gpus">GPUs on Compute Engine</a>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 31, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march312020</id>
    <updated>2020-03-31T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march312020"/>
    <content type="html"><![CDATA[<ul><li><p><strong>Beta:</strong> <a href="https://cloud.google.com/compute/docs/instances/collecting-diagnostic-information">Collect diagnostic information from Windows VMs</a>.</p></li>
<li><p>C2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Frankfurt, Germany <code dir="ltr" translate="no">europe-west3-a,b</code></li>
<li>Ashburn, Northern Virginia, USA <code dir="ltr" translate="no">us-east4-a</code></li></ul></li>
<li><p>N2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>The Dalles, Oregon, USA <code dir="ltr" translate="no">us-west1-a</code></li>
<li>Changua County, Taiwan <code dir="ltr" translate="no">asia-east1-c</code></li></ul></li>
<li><p>M1 megamem machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Eemshaven, Netherlands <code dir="ltr" translate="no">europe-west4-b</code></li></ul></li>
<li><p>M1 ultramem machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Ashburn, Northern Virginia, USA <code dir="ltr" translate="no">us-east4-a</code></li></ul></li>
<li><p>M2 ultramem machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Los Angeles, California, USA <code dir="ltr" translate="no">us-west2-a,c</code></li></ul></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 24, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march242020</id>
    <updated>2020-03-24T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march242020"/>
    <content type="html"><![CDATA[<ul><li><p>Committed use discounts no longer require specific ratios for cores and memory. Now you can create separate committed use discount contracts for either cores or memory. Separating cores and memory provides more flexibility and improved cost optimization. Learn more at <a href="https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts#purchasecommitment">Purchasing commitments for machine types</a>.</p></li>
<li><p>You can <a href="https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#preserving_instance_names">preserve the names</a> of your VM instances when rolling out updates in a managed instance group. This is <strong>Generally available</strong>.</p></li>
<li><p>You can <a href="https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#updating_selected_instances">update selected VM instances in a managed instance group</a>, with minimal disruption and in a controlled way. This is <strong>Generally available</strong>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 19, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march192020</id>
    <updated>2020-03-19T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march192020"/>
    <content type="html"><![CDATA[<ul><li><a href="https://cloud.google.com/compute/docs/machine-types#e2_machine_types">E2 machine types</a> are <strong>Generally available</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 16, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march162020</id>
    <updated>2020-03-16T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march162020"/>
    <content type="html"><![CDATA[<ul><li><p>N2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>London, England UK <code dir="ltr" translate="no">europe-west2-b</code></li></ul></li>
<li><p>C2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>St. Ghislain, Belgium <code dir="ltr" translate="no">europe-west1-c,d</code></li></ul></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 11, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march112020</id>
    <updated>2020-03-11T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march112020"/>
    <content type="html"><![CDATA[<ul><li><p>You can identify VM instances that are not being used with <a href="https://cloud.google.com/compute/docs/instances/viewing-and-applying-idle-vm-recommendations">idle VM recommendations</a>. Use these recommendations to reduce unused resources and reduce your compute bill. This feature is <strong>Beta</strong>.</p></li>
<li><p>In <strong>beta</strong>, you can create an instance with 16 or 24 local SSD partitions for 6 TB and 9 TB of local SSD space, respectively. With 24 local SSD partitions, performance can reach a combined total of 2.4 million read IOPS. For more information, see <a href="https://cloud.google.com/compute/docs/disks/local-ssd#capacity_9tb">9 TB Local SSD maximum capacity beta</a>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 09, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march_09_2020</id>
    <updated>2020-03-09T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march_09_2020"/>
    <content type="html"><![CDATA[<ul><li><a href="https://cloud.google.com/compute/docs/machine-images">Machine image</a> is now available in <strong>beta</strong>. You can use machine images to store configuration, metadata, permission, and data required to create a VM instance in a single resource.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 05, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march052020</id>
    <updated>2020-03-05T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march052020"/>
    <content type="html"><![CDATA[<ul><li>CoreOS Container Linux images will reach their end of life on May 26, 2020. For more information, see <a href="https://cloud.google.com/compute/docs/eol/coreOS">CoreOS End-Of-Life (EOL)</a>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 3, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march32020</id>
    <updated>2020-03-03T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march32020"/>
    <content type="html"><![CDATA[<ul><li>You can now create <a href="https://cloud.google.com/compute/docs/machine-types#e2_machine_types">E2 machine types</a> in all <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>March 2, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#march22020</id>
    <updated>2020-03-02T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#march22020"/>
    <content type="html"><![CDATA[<ul><li>You can now <a href="https://cloud.google.com/compute/docs/images/export-image#exporting_an_image_with_a_single_command">use the Google Cloud Console to export images to Cloud Storage</a>. This is <strong>Generally Available</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 27, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february272020</id>
    <updated>2020-02-27T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february272020"/>
    <content type="html"><![CDATA[<ul><li><p>E2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Los Angeles, USA <code dir="ltr" translate="no">us-west2-a,b,c</code></li>
<li>London, England, UK <code dir="ltr" translate="no">europe-west2-a,b,c</code></li>
<li>Frankfurt, Germany <code dir="ltr" translate="no">europe-west3-b,c</code></li>
<li>Tokyo, Japan <code dir="ltr" translate="no">asia-northeast1-a,b,c</code></li></ul></li>
<li><p>N2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Frankfurt, Germany <code dir="ltr" translate="no">europe-west3 a,b</code></li></ul></li>
<li><p>C2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Council Bluffs, Iowa, US <code dir="ltr" translate="no">us-central1-a</code></li></ul></li>
<li><p>M2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Mumbai, India <code dir="ltr" translate="no">asia-south1-a</code></li></ul></li>
<li><p>You can now manage, maintain, and view patch compliance for your VM instances using the OS patch management feature. For more information, see <a href="https://cloud.google.com/compute/docs/os-patch-management">OS patch management</a>. This feature is available in <strong>beta</strong>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 24, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february242020</id>
    <updated>2020-02-24T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february242020"/>
    <content type="html"><![CDATA[<ul><li>The <code dir="ltr" translate="no">us-west3</code> Salt Lake City, UT region is now available to all projects and users. The zones in the <code dir="ltr" translate="no">us-west3</code> region have the <a href="https://cloud.google.com/compute/docs/cpu-platforms">Skylake CPU platform</a>. See <a href="https://cloud.google.com/compute/docs/regions-zones">Regions and zones</a> for more information.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 21, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february212020</id>
    <updated>2020-02-21T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february212020"/>
    <content type="html"><![CDATA[<ul><li><p>NVIDIA® Tesla® T4 GPUs are now available in the following additional regions and zones:</p> <ul><li>Changhua County, Taiwan: <code dir="ltr" translate="no">asia-east1-a</code></li>
<li>London, England, UK: <code dir="ltr" translate="no">europe-west2-b</code></li></ul> <p>For information about using T4 GPUs on Compute Engine, see <a href="https://cloud.google.com/compute/docs/gpus">GPUs on Compute Engine</a>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 19, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february192020</id>
    <updated>2020-02-19T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february192020"/>
    <content type="html"><![CDATA[<ul><li><p>M2 machine types are now available in the following <a href="https://cloud.google.com/compute/docs/regions-zones#available">regions and zones</a>:</p> <ul><li>Northern Virginia <code dir="ltr" translate="no">us-east4-a,b</code></li></ul></li>
<li><p>If you have configured autohealing for your managed instance group, you can <a href="https://cloud.google.com/compute/docs/instance-groups/autohealing-instances-in-migs#checking_whether_instances_are_healthy">review the health state</a> of each VM in the group. This is <strong>Generally Available</strong>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 18, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february182020</id>
    <updated>2020-02-18T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february182020"/>
    <content type="html"><![CDATA[<ul><li>N2D machine types are available in beta. N2D machine types are built on top of second generation AMD EPYC Rome processors. They are a great fit for general purpose workloads and for workloads that require high memory bandwidth. Learn more about these <a href="https://cloud.google.com/compute/docs/machine-types#n2d_machine_types_beta">general purpose machine types</a>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 13, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february132020</id>
    <updated>2020-02-13T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february132020"/>
    <content type="html"><![CDATA[<ul><li><p>NVIDIA® Tesla® T4 GPUs are now available in the following additional regions and zones:</p> <ul><li>London, England, UK: <code dir="ltr" translate="no">europe-west2-a</code></li>
<li>Seoul, South Korea: <code dir="ltr" translate="no">asia-northeast3-b,c</code></li></ul> <p>For information about using T4 GPUs on Compute Engine, see <a href="https://cloud.google.com/compute/docs/gpus">GPUs on Compute Engine</a>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 12, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february122020</id>
    <updated>2020-02-12T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february122020"/>
    <content type="html"><![CDATA[<ul><li>You can now maintain consistent software configurations across VM instances using guest policies. For more information, see <a href="https://cloud.google.com/compute/docs/os-config-management">OS configuration management</a>. This feature is available in <strong>beta</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 11, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february112020</id>
    <updated>2020-02-11T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february112020"/>
    <content type="html"><![CDATA[<ul><li>To support a wide variety of BYOL scenarios, you can now <a href="https://cloud.google.com/compute/docs/instances/windows/bring-your-own-license">configure VMs to live migrate within a sole-tenant node group during host maintenance events</a>. This is available in <strong>Beta</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 07, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february072020</id>
    <updated>2020-02-07T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february072020"/>
    <content type="html"><![CDATA[<ul><li>G Suite administrators can now choose whether to include the domain suffix in usernames generated by the OS Login API. For more information, see <a href="https://cloud.google.com/compute/docs/oslogin/manage-oslogin-in-an-org#manage-oslogin-api">Managing the OS Login API</a>. This feature is <strong>Generally Available</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 5, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february52020</id>
    <updated>2020-02-05T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february52020"/>
    <content type="html"><![CDATA[<ul><li>Read an <a href="https://cloud.google.com/compute/docs/nodes/sole-tenancy-accounting-faq">FAQ</a> that can help you evaluate whether to classify <a href="https://cloud.google.com/compute/docs/nodes">sole-tenant node</a> payments as capital expenditures (CAPEX) or operational expenditures (OPEX).</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>February 3, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#february32020</id>
    <updated>2020-02-03T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#february32020"/>
    <content type="html"><![CDATA[<ul><li>You can build highly available deployments of stateful workloads on VM instances using <a href="https://cloud.google.com/compute/docs/instance-groups/stateful-migs">stateful managed instance groups (stateful MIGs)</a>. A stateful MIG preserves the unique state of each instance (instance name, attached persistent disks, and/or metadata) on machine restart, recreation, autohealing, or update. Stateful MIGs are available in <strong>beta</strong>.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>January 31, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#january312020</id>
    <updated>2020-01-31T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#january312020"/>
    <content type="html"><![CDATA[<ul><li><p>You can now <a href="https://cloud.google.com/compute/docs/nodes/vm-tenancy">reschedule VMs on, off, or between sole-tenant nodes</a>. This is <strong>Generally Available</strong>.</p></li>
<li><p>You can now enable an <a href="https://cloud.google.com/compute/docs/nodes/node-group-autoscaler">autoscaler</a> on your sole-tenant node groups. This is available in <strong>Beta</strong>.</p></li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>January 24, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#january242020</id>
    <updated>2020-01-24T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#january242020"/>
    <content type="html"><![CDATA[<ul><li>The <code dir="ltr" translate="no">asia-northeast3</code> Seoul region is now available to all projects and users. The zones in the <code dir="ltr" translate="no">asia-northeast3</code> region have the <a href="https://cloud.google.com/compute/docs/cpu-platforms">Skylake CPU platform</a>. See <a href="https://cloud.google.com/compute/docs/regions-zones">Regions and zones</a> for more information.</li></ul>]]>
    </content>
  </entry>

  <entry>
    <title>January 21, 2020</title>
    <id>tag:google.com,2016:compute-engine-release-notes#january212020</id>
    <updated>2020-01-21T00:00:00+00:00</updated>
    <link rel="alternate" href="https://docs.cloud.google.com/compute/docs/release-notes#january212020"/>
    <content type="html"><![CDATA[<ul><li><p>NVIDIA® Tesla® T4 GPUs are now available in the following additional zones:</p> <ul><li>Tokyo: <code dir="ltr" translate="no">asia-northeast1-c</code></li>
<li>Singapore: <code dir="ltr" translate="no">asia-southeast1-c</code></li>
<li>Iowa: <code dir="ltr" translate="no">us-central1-f</code></li>
<li>Mumbai: <code dir="ltr" translate="no">asia-south1-a</code></li></ul> <p>For information about using T4 GPUs on Compute Engine, see <a href="https://cloud.google.com/compute/docs/gpus">GPUs on Compute Engine</a>.</p></li>
<li><p>You can temporarily turn off or restrict managed instance group autoscaling. The autoscaler's configuration remains intact, and all autoscaling activities resume when you turn it on again or lift the restriction. <a href="https://cloud.google.com/compute/docs/autoscaler/managing-autoscalers#disable_or_restrict_an_autoscaler">Turning off or restricting autoscaling</a> for managed instance groups is now <strong>Generally available</strong>.</p></li></ul>]]>
    </content>
  </entry>


</feed>
