GCP Release Notes: February 09, 2026

AlloyDB for PostgreSQL

Fixed

We are announcing the release of support for the AlloyDB language connectors and Auth Proxy with Auto IAM Authentication and managed connection pooling. This feature and the fix for the issue from below is available starting with maintenance version 20260107.02_05. Clusters with a maintenance window that may not have received this release can use self-service maintenance to perform a maintenance update.

Cloud Asset Inventory

Feature

The following resource types are publicly available through the ExportAssets, ListAssets, BatchGetAssetsHistory, QueryAssets, Feed, SearchAllResources, and SearchAllIamPolicies APIs.

• Cloud Run
  • run.googleapis.com/WorkerPool
• Dataform
  • dataform.googleapis.com/TeamFolder
  • dataform.googleapis.com/Folder
• Discovery Engine
  • discoveryengine.googleapis.com/Assistant

Cloud Data Fusion

Feature

Cloud Data Fusion version 6.11.1.1 is generally available (GA). This release includes the following feature:

• InstanceV3 monitored-resource: Introduced datafusion.googleapis.com/InstanceV3 as the default monitored resource for instance-level metrics and system service logs. This resource excludes the org_id and namespace labels found in InstanceV2. Emission of InstanceV2 metrics and logs is disabled by default for new and upgraded instances but can be re-enabled using the REST API.

  For more information, see Metrics overview and View pipeline logs.

Fixed

Fixed in Cloud Data Fusion 6.11.1.1:

• Fixed retries in message publishing when the messaging service is temporarily unavailable (CDAP-21043).
• Fixed a security vulnerability where user-provided code in preview runners could access sensitive data from other preview runs (CDAP-21211).
• Fixed an issue where internal task workers running user code could hang indefinitely. The system now forces completed tasks to exit and uses a health check to restart unresponsive workers (CDAP-21213).
• Fixed an issue where the list apps API endpoint failed to return all deployed pipelines when used with pagination (CDAP-21220).

Cloud Logging

Feature

You can use the Cloud Logging API MCP server to let agents and AI applications interact with your log entries. This feature is in Preview.

Cloud SQL for MySQL

Feature

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

Cloud SQL for PostgreSQL

Feature

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

Cloud SQL for SQL Server

Feature

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

Cloud Service Mesh

Announcement

The following images are now rolling out for managed Cloud Service Mesh:

• 1.21.6-asm.10 is rolling out to the rapid release channel.
• 1.20.8-asm.63 is rolling out to the regular release channel.
• 1.19.10-asm.57 is rolling out to the stable release channel.

These patch releases contain the fixes for the following managed Cloud Service Mesh CVEs:

CVE	Proxy	Control Plane	CNI	Distroless	Severity
CVE-2025-61729	Yes	Yes	–	Yes	High (7.5)
CVE-2025-61727	Yes	Yes	–	Yes	Medium (6.5)
CVE-2024-41996	Yes	Yes	–	Yes	High (7.5)
CVE-2025-9086	Yes	Yes	–	Yes	High (7.5)
CVE-2021-46848	Yes	Yes	–	Yes	Critical (9.1)
CVE-2025-13151	Yes	Yes	–	Yes	High (7.5)
CVE-2025-68973	Yes	Yes	–	Yes	High (7.8)

Compute Engine

Feature

You can autoscale a managed instance group (MIG) that has instance flexibility configured. Autoscaling lets the MIG create or delete virtual machine instances based on an increase or decrease in load. For more information, see About instance flexibility.

Document AI

Feature

Layout parser model pretrained-layout-parser-v1.6-2026-01-13 powered by Gemini 3 Flash LLM is available in Preview.

This processor version has ML processing capabilities in the US and EU.

For more information about available models, see the custom extractor page.

Gemini Enterprise

Feature

Gemini Enterprise: Data connector for Notion (Public preview)

You can connect Notion data stores to Gemini Enterprise. For more information, see Connect Notion.

Support for Notion data sources is in Public preview.

Google SecOps

Announcement

Enhanced rule observability: New metadata, visual indicators, and dashboards

Google Security Operations has introduced updates to how detection and alert data is processed and visualized. These changes help Google SecOps teams distinguish between primary rule runs and rule replays, which provides clarity on detection delays and the impact of late-arriving enrichment data.

• Key improvements

  • Enhanced metadata: Detection and alert objects now include specific metadata that identifies whether they were produced during a primary rule run, or as part of a rule replay or retrohunt.
  • Improved troubleshooting: This data lets Google SecOps teams definitively answer critical operational questions, such as the cause of perceived detection delays or the specific impact of late-arriving enrichment data on active rules.
  • Rule replay insights: Learn more about the distinction between primary runs and replays to manage the re-enrichment of Unified Data Model (UDM) events. For detailed definitions and technical workflows, see Understand rule replay and Understand rule detection delays.
  • New detection dashboard: To support these backend metadata changes, a new Detection Health dashboard is now available. This interface provides a visual representation of rule performance and replay status, letting teams monitor detection health more effectively.
  • Custom reporting: There are new fields available in the Detections schema, letting you build custom dashboards.

• New metadata and third-party integration: Detections and alerts now emit specific metadata to help customers track timing and latency. This data is available for integration with third-party systems using the following fields:

  • detectionTimingDetails: An enum identifying the run type:
  • DETECTION_TIMING_DETAILS_REPROCESSING
  • DETECTION_TIMING_DETAILS_RETROHUNT
  • DETECTION_TIMING_DETAILS_UNSPECIFIED
  • latencyMetrics: Includes timestamps for oldestIngestionTime, newestIngestionTime, oldestEventTime, and newestEventTime.

• Enhanced platform and visual indicators:

  • Alerts and rule details: A new visual indicator in the Detection Type column provides granular details on hover.
  • Filter facets: The Alerts lister page now includes detection timing details as a filterable facet.
  • SOAR integration: In the Case Overview, the Composite Detections table now carries through the same iconography for a consistent investigation experience.

Google SecOps SIEM

Announcement

Enhanced rule observability: New metadata, visual indicators, and dashboards

Google Security Operations has introduced updates to how detection and alert data is processed and visualized. These changes help Google SecOps teams distinguish between primary rule runs and rule replays, which provides clarity on detection delays and the impact of late-arriving enrichment data.

• Key improvements

  • Enhanced metadata: Detection and alert objects now include specific metadata that identifies whether they were produced during a primary rule run, or as part of a rule replay or retrohunt.
  • Improved troubleshooting: This data lets Google SecOps teams definitively answer critical operational questions, such as the cause of perceived detection delays or the specific impact of late-arriving enrichment data on active rules.
  • Rule replay insights: Learn more about the distinction between primary runs and replays to manage the re-enrichment of Unified Data Model (UDM) events. For detailed definitions and technical workflows, see Understand rule replays and Understand rule detection delays.
  • New detection dashboard: To support these backend metadata changes, a new Detection Health dashboard is now available. This interface provides a visual representation of rule performance and replay status, letting teams monitor detection health more effectively.
  • Custom reporting: There are new fields available in the Detections schema, letting you build custom dashboards.

• New metadata and third-party integration: Detections and alerts now emit specific metadata to help customers track timing and latency. This data is available for integration with third-party systems using the following fields:

  • detectionTimingDetails: An enum identifying the run type:
  • DETECTION_TIMING_DETAILS_REPROCESSING
  • DETECTION_TIMING_DETAILS_RETROHUNT
  • DETECTION_TIMING_DETAILS_UNSPECIFIED
  • latencyMetrics: Includes timestamps for oldestIngestionTime, newestIngestionTime, oldestEventTime, and newestEventTime.

• Enhanced platform and visual indicators:

  • Alerts and rule details: A new visual indicator in the Detection Type column provides granular details on hover.
  • Filter facets: The Alerts lister page now includes detection timing details as a filterable facet.
  • SOAR integration: In the Case Overview, the Composite Detections table now carries through the same iconography for a consistent investigation experience.

Announcement

Enhanced rule observability: New metadata, visual indicators, and dashboards

Google Security Operations has introduced updates to how detection and alert data is processed and visualized. These changes help Google SecOps teams distinguish between primary rule runs and rule replays, which provides clarity on detection delays and the impact of late-arriving enrichment data.

• Key improvements

  • Enhanced metadata: Detection and alert objects now include specific metadata that identifies whether they were produced during a primary rule run, or as part of a rule replay or retrohunt.
  • Improved troubleshooting: This data lets Google SecOps teams definitively answer critical operational questions, such as the cause of perceived detection delays or the specific impact of late-arriving enrichment data on active rules.
  • Rule replay insights: Learn more about the distinction between primary runs and replays to manage the re-enrichment of Unified Data Model (UDM) events. For detailed definitions and technical workflows, see Understand rule replays and Understand rule detection delays.
  • New detection dashboard: To support these backend metadata changes, a new Detection Health dashboard is now available. This interface provides a visual representation of rule performance and replay status, letting teams monitor detection health more effectively.
  • Custom reporting: There are new fields available in the Detections schema, letting you build custom dashboards.

• New metadata and third-party integration: Detections and alerts now emit specific metadata to help customers track timing and latency. This data is available for integration with third-party systems using the following fields:

  • detectionTimingDetails: An enum identifying the run type:
  • DETECTION_TIMING_DETAILS_REPROCESSING
  • DETECTION_TIMING_DETAILS_RETROHUNT
  • DETECTION_TIMING_DETAILS_UNSPECIFIED
  • latencyMetrics: Includes timestamps for oldestIngestionTime, newestIngestionTime, oldestEventTime, and newestEventTime.

• Enhanced platform and visual indicators:

  • Alerts and rule details: A new visual indicator in the Detection Type column provides granular details on hover.
  • Filter facets: The Alerts lister page now includes detection timing details as a filterable facet.
  • SOAR integration: In the Case Overview, the Composite Detections table now carries through the same iconography for a consistent investigation experience.

Looker

Feature

The Looker Action Hub has been updated to support newer API versions for Google Ads (from v19 to v22) and Facebook Custom Audiences (from v22 to v24).

Feature

The Customer Engineer Advanced Editor default role now includes the gemini_in_looker, chat_with_agent, chat_with_explore, and save_agents permissions, which grant access to Gemini features and Conversational Analytics functionality.

Breaking

When you use Elite System Activity, all System Activity fields of the longtext type that have a size greater than 2 MB will be truncated. If a table has only one column with a longtext type, that column will be set to a maximum of 1.9 MB in size. If a table has multiple columns of the longtext type, the total maximum size across all such columns is 2 MB, and this limit is distributed uniformly among those columns. For example, if a table has x longtext columns, each column will have a maximum length of 2 MB divided by x.

Fixed

An issue has been fixed where some drill links could fail to work when cookieless embed was enabled. This feature now performs as expected.

Feature

When you use Elite System Activity, the merge_query table now refreshes every 10 minutes.

Feature

When you are delivering content to an SFTP server, additional key exchange algorithms and host key algorithms are now supported.

Fixed

An issue has been fixed where the pagination option was not being displayed in the LookML Dashboards folder for some users. This feature now performs as expected.

Fixed

An issue has been fixed where custom dimensions that were based on numeric fields could be converted to strings, which caused incorrect sorting. This feature now performs as expected.

Fixed

An issue has been fixed where choosing a non-default color collection and then choosing a custom color in a conditional formatting rule could cause the rule to revert to the default color collection. This feature now performs as expected.

Announcement

Looker 26.2 is expected to include the following changes, features, and fixes:

• Expected Looker (original) deployment start: Monday, February 9, 2026
• Expected Looker (original) final deployment and download available: Monday, February 16, 2026
• Expected Looker (Google Cloud core) deployment start: Monday, February 9, 2026
• Expected Looker (Google Cloud core) final deployment: Friday, February 27, 2026

Fixed

An issue has been fixed where a modification to the color palette for the “Along a scale…” conditional formatting feature could fail to be saved. This feature now performs as expected.

Feature

Now available in preview, Looker has full support for connections with AlloyDB for PostgreSQL. When you create a connection in Looker, you can now select “Google Cloud AlloyDB for PostgreSQL” from the Dialect drop-down menu. This update does not affect existing AlloyDB connections that were created using the PostgreSQL 9.5+ option in the Dialect menu.

Fixed

An issue has been fixed where non-admin users could not favorite LookML dashboards. This feature now performs as expected.

Feature

The user attribute pairing user interface for SAML, LDAP, and OpenID Connect authentication has been updated. A new “Manage Pairings” side panel provides a robust interface for adding, removing, and viewing attribute pairings. This new interface also includes filtering and pagination and allows for a single claim to be associated with multiple Looker user attributes.

Fixed

An issue has been fixed where Looker could return a 500 error if a user with one or more single quotes in their name attempted to commit LookML. This feature now performs as expected.

Fixed

An issue has been fixed where switching a visualization type from Table to Single Value could carry over unwanted conditional formatting. This feature now performs as expected.

Fixed

An issue has been fixed where conditional formatting no longer appeared on certain dashboard tiles. This feature now performs as expected.

Fixed

An issue has been fixed where changing the collection in a conditional formatting rule could reset styles for the rule. This feature now performs as expected.

Fixed

An issue has been fixed where the filter bar would automatically expand on dashboard load when the filter location was set to “Right”. This feature now performs as expected.

Fixed

An issue has been fixed where switching filter types from Matches (Advanced) to another filter type could populate that filter with an incorrect filter configuration. This feature now performs as expected.

Fixed

An issue has been fixed where adding a new field to a conditionally formatted result set could fail to apply the conditional formatting to the new field. This feature now performs as expected.

Fixed

An issue has been fixed where dashboard tiles with titles that included the % symbol could not be downloaded in the Safari 26.0 browser. This feature now performs as expected.

Feature

Looker admins can now grant essential Google Cloud services, such as Conversational Analytics, access to a Looker instance, even when an IP allowlist is active.

Feature

Looker admins can now enforce a password expiration policy, enhancing security for users who authenticate with an email and a password. This new feature lets admins set a password expiration window between 30 and 365 days. Fourteen days before password expiration, a banner will notify the user, and, once their password has expired, the user must reset it at the next login.

Virtual Private Cloud

Feature

You can bring your own IPv6 global unicast addresses (GUAs) to assign to a subnet’s internal IPv6 address range. Although GUAs are typically public addresses, in this configuration they are used privately and function in the same way as Google Cloud-provisioned ULAs.

For more information, see Bring your own IP addresses.

Source: Google Cloud Platform