Apigee API hub
Changed
Create and manage API operations in the UI
You can now create and manage API operations for your API versions from the API details page in the Google Cloud console.
For more information, see Manage operations.
Apigee APIM Operator
Announcement
On October 16, 2025, we released an updated version of Apigee (1-16-0-apigee-3).
Fixed
| Bug ID | Description |
|---|---|
| 442501403 | Fixed an issue that caused incorrect target latency metrics in Apigee Analytics when a TargetEndpoint is configured with a <LoadBalancer>. |
| 437999897 | Reduced the log level for failed geo IP lookups to address excessive log messages for private IP addresses. |
| 436323210 | Fixed ingress cert keys to allow both tls.key/key and tls.crt/cert. |
| N/A | Updates to security infrastructure and libraries. |
Security
| Bug ID | Description |
|---|---|
| 440419558, 433759657 | Security fix for Apigee infrastructure. This addresses the following vulnerabilities: |
Apigee X
Announcement
On October 16, 2025, we released an updated version of Apigee (1-16-0-apigee-3).
Fixed
| Bug ID | Description |
|---|---|
| 442501403 | Fixed an issue that caused incorrect target latency metrics in Apigee Analytics when a TargetEndpoint is configured with a <LoadBalancer>. |
| 437999897 | Reduced the log level for failed geo IP lookups to address excessive log messages for private IP addresses. |
| 436323210 | Fixed ingress cert keys to allow both tls.key/key and tls.crt/cert. |
| N/A | Updates to security infrastructure and libraries. |
Security
| Bug ID | Description |
|---|---|
| 440419558, 433759657 | Security fix for Apigee infrastructure. This addresses the following vulnerabilities: |
BigQuery
Feature
The following features are now generally available (GA) in BigQuery Studio:
To streamline resource discovery and access, the left Explorer pane has been reorganized into three sections: Explorer, Classic Explorer, and Git repository. You can still use the Classic Explorer, which provides the complete resources tree.
In the Explorer pane, you can use the search feature to find BigQuery resources in your organization. The results appear in a new tab in the details pane. You can use filters to narrow your search.
You can access job histories by clicking Job history in the Explorer pane. A new tab opens that displays a list of job histories. BigQuery Studio no longer has a bottom pane for job history.
To reduce tab proliferation, clicking a resource opens it within the same tab. To open the resource in a separate tab, press Ctrl (or Command on macOS) and click the resource. To prevent the current tab from getting its content replaced, double-click the tab. The name changes from italicized to regular font. If you still lose your resource, you can click tab_recent Recent tabs in the details pane to find the resource.
You can use breadcrumbs to navigate through different tabs and resources in the details pane.
In the Home tab, the What’s new section contains a list of new capabilities and changes to the BigQuery Studio.
The notebook action bar is consolidated by default to give you more screen space for writing code.
Feature
You can now access repositories by clicking Repositories in the Explorer pane. A new tab opens that displays a list of repositories. The Explorer pane no longer has a bottom pane for repositories. When you open a workspace in a repository, it opens in the Git repository pane in the left pane. These features are available in BigQuery Studio in preview.
Cloud Service Mesh
Announcement
The promotion of 1.21 to the Rapid release channel included upstream breaking changes to ExternalName and auto-sni when using the ISTIOD implementation. After considering the impact on customers, we have decided to restore the previous behavior from 1.20 and earlier for managed Cloud Service Mesh clusters using the ISTIOD implementation to match Rapid clusters using the TRAFFIC_DIRECTOR implementation. These changes are rolling out to the Rapid release channel in version 1.21.5-asm.55 or later.
If you are using an
ExternalNameservice in the Rapid channel without a port description, theExternalNameservice will not be translated intoClusterin the Envoy configuration. If theExternalNameservice is a destination ofVirtualServiceorExternalNameservice is used withREGISTRY_ONLYmode, you must specify the port in the service like in 1.20 and earlier.If you have an external service multiplexing traffic based on SNI but the corresponding
DestinationRuledoesn’t have an explicit SNI, you must set SNI properly.
Compute Engine
Changed
Starting with SUSE Linux Enterprise Server (SLES) 16, including variants for SAP,
the default file system for the root partition (/) is Btrfs
changing from the previous default of XFS. For more information, see File systems in SLES
in the SUSE documentation.
Config Connector
Announcement
Config Connector version 1.137.0 is now available.
Changed
New Beta Resources (Direct Reconciler):
DocumentAIProcessorVersionEssentialContactsContactBigQueryBigLakeTableBackupDRBackupPlan
Changed
New Alpha Resources (Direct Reconciler):
BigtableMaterializedView
Feature
New Fields:
BigtableMaterializedView: Addedspec.sourceTableRefandspec.definition.BackupDRBackupPlan: Addedspec.backupConfig.retentionPeriodDaysandspec.backupConfig.backupWindow.MemorystoreInstance: Added support forMEMCACHEandREDISinstance types.
Changed
Reconciliation Improvements:
- Enabled opt-in for IAM partial policy management.
- Enabled server-side apply for KMS resources.
- Improved reconciliation for
BigtableLogicalViewby using deep reflection. - Improved reconciliation for
FirestoreDatabasewith identity pattern and export support. - Improved reconciliation for
RunJobwith export support. - Unified
ComputeTargetTCPProxydirect API and controller.
Fixed
Bug Fixes:
- Fixed an issue where
ComputeBackendServicebackends were not sorted. - Fixed an issue where
CloudFunctionsFunctionruntime was not a supported value. - Fixed an issue with labels for
BackupDRBackupPlan. - Fixed an issue with labels for
RunJob. - Fixed a fuzzing issue for
FirestoreField. - Fixed an issue with
KMSCryptoKeyimport. - Fixed a flakiness issue in the
MonitoringDashboardfuzzer. - Fixed a flakiness issue in tests.
- Fixed an issue with bad labels in tests.
- Fixed an issue with
etagin direct reconciliation.
Generative AI on Vertex AI
Feature
vLLM TPU
vLLM TPU, a highly-efficient serving framework for large language models (LLM) that’s optimized for Cloud TPU hardware, is available through Model Garden.
Looker Studio
Feature
Pro feature: Share and schedule reports with Slack
You can now send Looker Studio reports to Slack channels and Slack users on your Slack workspaces. This feature is only available to Looker Studio Pro users, and is available in Preview.
Feature
Vertical stacking in responsive reports
Responsive reports now support vertical stacking. You can add multiple components to a column within a section. Learn more about creating responsive reports.
Policy Intelligence
Feature
You can use Policy Troubleshooter to remediate access issues. This feature is available in Preview.
Security Command Center
Changed
Security Command Center and attack path simulations use Compute Engine and Google Kubernetes Engine operating system and software vulnerabilities to detect toxic combinations and chokepoints.
Source: Google Cloud Platform


![Microsoft Teams: Join by code requires owner approval for private teams [MC1183610] 3 pexels pixabay 461169](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-461169-150x150.webp)
![Rate my call feedback experience update in Microsoft Teams [MC1183608] 4 pexels rostislav 5011647](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-rostislav-5011647-150x150.webp)
![Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF) [MC1183611] 5 pexels ben neale 123878 380337](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-ben-neale-123878-380337-150x150.webp)