Apigee X
Announcement
On February 24th, 2026, we released an updated version of Apigee (1-17-0-apigee-3).
Security
| Bug ID | Description |
|---|---|
| 481735779, 457138941, 471232237 | Security fix for Apigee infrastructure. This addresses the following vulnerabilities: |
| 485543125 | Apigee no longer supports the following TLS_RSA cipher suites:
|
Fixed
| Bug ID | Description |
|---|---|
| 470375542 | Fixed a memory leak which could result in a spike in 503 responses with no_healthy_upstream messages. |
| 480997525 | Applied a fix for proxy calls failing with The URI contains illegal characters error after Netty upgrade. |
| 485595627 | Fixed an issue resulting in TLS handshake errors. |
BigQuery
Feature
You can now create and review custom glossary terms in BigQuery for a conversational analytics agent and you can review business glossary terms imported from Dataplex Universal Catalog for an agent. These terms help an agent interpret your prompts.
This feature is now in Preview.
Cloud Asset Inventory
Feature
The following resource types are publicly available through the ExportAssets, ListAssets, BatchGetAssetsHistory, QueryAssets, Feed, SearchAllResources, and SearchAllIamPolicies APIs.
- Cloud Load Balancing
networksecurity.googleapis.com/AuthzPolicy
- Network Services API
networkservices.googleapis.com/AuthzExtension
Cloud Run
Feature
You can use the Cloud Run remote MCP server to let agents and AI applications deploy with Cloud Run (Preview).
Feature
Deploy a highly available, multi-region Cloud Run service with automated failover and failback for external traffic using Cloud Run service health (Preview).
Cloud Run functions
Feature
Support for the ability to configure Direct VPC egress for 2nd gen functions is in General Availability.
Cloud SQL for MySQL
Feature
It now takes less time to create a Cloud SQL instance when point-in-time recovery (PITR) is enabled, as it is by default in the Google Cloud console. During instance creation, PITR now initially uses an instant snapshot instead of a standard backup. and then later converts the snapshot to a standard backup in the background to support restore operations.
Cloud SQL for PostgreSQL
Feature
It now takes less time to create a Cloud SQL instance when point-in-time recovery (PITR) is enabled, as it is by default in the Google Cloud console. During instance creation, PITR now initially uses an instant snapshot instead of a standard backup. and then later converts the snapshot to a standard backup in the background to support restore operations.
Cloud Translation
Change
Translation LLM now supports full finetuning with LoRA.
Gemini
Announcement
Finish changes feature in IntelliJ general availability
The finish changes features is now generally available (GA).
Announcement
File outline feature in IntelliJ general availability
The file outline feature is now generally available (GA).
Announcement
Finish changes feature in IntelliJ general availability
The finish changes features is now generally available (GA).
Announcement
File outline feature in IntelliJ general availability
The file outline feature is now generally available (GA).
Google Kubernetes Engine
Feature
You can create a bare metal instance from the C4A machine series with the c4a-highmem-96-metal machine type. This machine type is available in Public Preview for Standard clusters running GKE version 1.35.0-gke.2232000 or later. You can select this machine type by using the --machine-type flag when creating a cluster or node pool. For more information about the requirements and limitations of this machine type, see the Requirements and limitations section of the “Arm workloads on GKE” document.
Feature
The release note for November 11, 2025 has been updated to correct the version requirements for using N4D machine types. Cluster autoscaler was incorrectly included in the list of features requiring GKE version 1.34.1-gke.2037000 or later. You can use any available GKE version to use N4D and Cluster autoscaler.
Change
Expanded coverage for compute flexible committed use discounts (CUDs) is available to all Cloud Billing accounts. All Cloud Billing accounts have been automatically migrated to the new spend-based CUD model and you no longer need to opt in to benefit from the expanded coverage. For the full list of eligible SKUs across Compute Engine, GKE, and Cloud Run, see SKU Groups – Compute Flexible CUD Eligible SKUs.
To learn more about compute flexible CUDs and how they apply to your GKE usage, see the GKE CUDs documentation.
Google SecOps
Feature
New: cross joins in multi-stage queries
You can now use cross joins in YARA-L 2.0 multi-stage queries let you compare individual UDM event data against aggregated statistics calculated in previous YARA-L stages. They are supported in:
- Search
- Dashboards
For more information, see Cross joins in multi-stage queries.
Feature
RBAC for ingestion metrics
Administrators can now use RBAC for ingestion metrics to restrict visibility of system health data, such as ingestion volume, errors, and throughput, based on a user’s business scope.
The Data Ingestion and Health dashboard now uses Data Access scopes. When a scoped user loads the dashboard, the system automatically filters metrics to show only data that matches their assigned labels: Namespace, Log Type, and Ingestion Source.
For more information, see Ingestion metrics.
Google SecOps SIEM
Feature
New: cross joins in multi-stage queries
You can now use cross joins in YARA-L 2.0 multi-stage queries let you compare individual UDM event data against aggregated statistics calculated in previous YARA-L stages. They are supported in:
- Search
- Dashboards
For more information, see Cross joins in multi-stage queries.
Feature
New: cross joins in multi-stage queries
You can now use cross joins in YARA-L 2.0 multi-stage queries let you compare individual UDM event data against aggregated statistics calculated in previous YARA-L stages. They are supported in:
- Search
- Dashboards
For more information, see Cross joins in multi-stage queries.
Feature
RBAC for ingestion metrics
Administrators can now use RBAC for ingestion metrics to restrict visibility of system health data, such as ingestion volume, errors, and throughput, based on a user’s business scope.
The Data Ingestion and Health dashboard now uses Data Access scopes. When a scoped user loads the dashboard, the system automatically filters metrics to show only data that matches their assigned labels: Namespace, Log Type, and Ingestion Source.
For more information, see Ingestion metrics.
Feature
RBAC for ingestion metrics
Administrators can now use RBAC for ingestion metrics to restrict visibility of system health data, such as ingestion volume, errors, and throughput, based on a user’s business scope.
The Data Ingestion and Health dashboard now uses Data Access scopes. When a scoped user loads the dashboard, the system automatically filters metrics to show only data that matches their assigned labels: Namespace, Log Type, and Ingestion Source.
For more information, see Ingestion metrics.
Oracle Database@Google Cloud
Feature
For Autonomous Database Service, Oracle Database@Google Cloud supports the asia-northeast2 (Osaka, Japan) region.
For a list of supported locations, see Supported regions and zones.
Vertex AI Search
Feature
Vertex AI Search: Change the pricing model for a project
There are two pricing models for apps and data stores: the general model (pay-as-you-go consumption-based) and the configurable subscription model (a monthly subscription).
You can switch from configurable pricing to general pricing for a project if all its data stores and apps use the general model. For more information, see Disable configurable pricing for project.
Source: Google Cloud Platform
