# Google Cloud Daily Brief: 9 service updates

- Cloud: Google Cloud
- Date: 2026-10-31
- Canonical page: https://jonathanglass.cloud/whats-new/gcp/2026-10-31.html
- Dataset: https://jonathanglass.cloud/data/gcp/daily_summaries.json

## Google Cloud Daily Security & IaC Update

As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key updates, focusing on their security implications and Infrastructure as Code (IaC) availability.

### 1. BigQuery: Apache Arrow Format for Query Results (Preview)
*   **Feature & Security Summary**: This update introduces support for retrieving BigQuery query results directly in Apache Arrow format. This was introduced to significantly accelerate data retrieval for analytical workloads, particularly beneficial for data scientists and machine learning engineers who need efficient, in-memory columnar data processing. By reducing serialization and deserialization overhead, it streamlines data pipelines. From a security and compliance perspective, while not a direct security feature, faster data processing enables quicker security analytics, threat detection, and compliance reporting by accelerating data ingestion into other tools. Data remains within BigQuery's robust security model, ensuring governance and access controls are maintained.
*   **Terraform Availability**: Supported via the `hashicorp/google` provider, primarily through the `google_bigquery_job` resource for managing query execution. This feature is supported in provider versions `5.0+`, with initial support from `4.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigquery_job)

### 2. Apigee hybrid: Critical Security & Stability Fixes
*   **Feature & Security Summary**: Apigee hybrid has received crucial updates addressing several security and stability issues. Key fixes include resolving a regression where `apigee-connect-agent` ignored `HTTPS_PROXY` settings, which is vital for ensuring all outbound traffic adheres to organizational network security policies and passes through required proxies for inspection and control. Compromised emSign/Comodo roots have been removed from trust stores, significantly enhancing supply chain security by preventing potential man-in-the-middle attacks and ensuring only trusted certificates are recognized. Additionally, corrections were made to `x-envoy-decorator-operation` header forwarding and LLM token quota flow variable assignment, improving API gateway reliability. Most importantly, multiple CVEs in core Apigee hybrid containers have been patched, directly reducing the attack surface and mitigating known vulnerabilities. These updates are critical for maintaining a strong security posture, compliance with network policies, and overall platform integrity for hybrid API deployments.
*   **Terraform Availability**: Management of Apigee organizations and related configurations is supported by the `hashicorp/google` provider using the `google_apigee_organization` resource. This update's underlying platform fixes are reflected in provider version `1.16.13`, with initial support from `1.0`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_organization)

### 3. Google Cloud SQL: Enhanced Backup Plan Modification
*   **Feature & Security Summary**: This new feature for Cloud SQL enables users to modify existing backup plans with greater flexibility. Specifically, it allows for updating settings such as backup rules (e.g., frequency, time) and adjusting the maximum custom on-demand retention periods. This was introduced to provide more granular control and adaptability for data recovery strategies, aligning with evolving business requirements and regulatory compliance. From a security and compliance perspective, this enhancement directly contributes to improved data resilience and disaster recovery capabilities. Granular control over backup policies helps organizations meet stringent Recovery Point Objective (RPO) and Recovery Time Objective (RTO) targets, and ensures compliance with data retention regulations by allowing precise configuration of backup schedules and retention periods for sensitive data.
*   **Terraform Availability**: Cloud SQL instance configurations, including backup settings, are managed via the `hashicorp/google` provider using the `google_sql_database_instance` resource. This feature is supported in provider versions `5.20.0`, with initial support from `4.0.0`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance)

### 4. Cloud Run: GPU-Enabled Jobs (Preview)
*   **Feature & Security Summary**: Cloud Run now supports running jobs with GPUs enabled for up to 12 hours (Preview). This expansion was introduced to enable Cloud Run to handle compute-intensive workloads that benefit significantly from GPU acceleration, such as machine learning inference, data processing, and scientific simulations, within a serverless and managed environment. From a security and compliance standpoint, while the feature itself is about compute capability, it allows organizations to execute high-performance, specialized workloads securely within Cloud Run's isolated and managed infrastructure. This means GPU-accelerated tasks benefit from Cloud Run's inherent security features, including container isolation, built-in IAM integration for fine-grained access control, and automatic patching, ensuring that sensitive data processing occurs in a controlled and secure environment without the operational overhead of managing underlying infrastructure.
*   **Terraform Availability**: Cloud Run jobs are managed using the `hashicorp/google` provider via the `google_cloud_run_v2_job` resource. This feature is supported in provider versions `5.0+`, with initial support from `4.0+`. [Terraform Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_job)

As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:

### Google Cloud Updates & Terraform Availability (October 30, 2026)

*   **Google Cloud Bigtable - Knowledge Catalog Integration GA**
    *   **Feature & Security Summary**: This update introduces the general availability (GA) of Bigtable's integration with Knowledge Catalog. This was introduced to significantly enhance metadata management and data asset visibility for Bigtable users. It allows for the discovery and search of specific Bigtable data assets, including authorized views, logical views, and continuous materialized views, directly within Knowledge Catalog. This capability centralizes the discovery of Bigtable's granular data structures alongside its instances and tables. From a security and compliance perspective, this integration provides a unified view of data assets, making it easier to track, audit, and govern sensitive data. It improves data lineage understanding, aids in compliance reporting by centralizing metadata, and helps enforce data access policies by providing better context on data usage. This is a critical step towards robust data governance and meeting regulatory requirements.
    *   **Terraform Availability**: This specific integration for discovering Bigtable views within Knowledge Catalog is not directly exposed as a dedicated resource in the `hashicorp/google` Terraform provider. While `google_bigtable_instance` and `google_bigtable_table` manage Bigtable resources, and `google_data_catalog_entry_group`, `google_data_catalog_entry`, `google_data_catalog_tag_template` manage Data Catalog components, the direct linkage for *discovering Bigtable views* is a service-level integration rather than a configurable IaC resource. Therefore, direct Terraform support for this specific integration is not available. (Supported: false, Latest Version: N/A, First Version: N/A, Provider Doc: N/A)

*   **Cloud SQL for PostgreSQL - Updated Time Zone Rules**
    *   **Feature & Security Summary**: This update addresses time zone rules for specific Canadian provinces/territories, reflecting permanent standard offsets. This was introduced to ensure the accuracy and consistency of time-sensitive data within Cloud SQL for PostgreSQL instances. Incorrect time zone handling can lead to data integrity issues, misaligned timestamps, and potential compliance violations, especially for applications dealing with financial transactions, logging, or scheduling across different regions. The update, available in PostgreSQL maintenance release `*.R20260712.01_44` or later, ensures that all time-based operations and data storage accurately reflect the local time, preventing operational discrepancies and supporting reliable auditing and reporting.
    *   **Terraform Availability**: Cloud SQL for PostgreSQL instances are managed by the `google_sql_database_instance` resource. While the specific maintenance release is applied by Google Cloud, Terraform can manage the instance configuration, including `database_version` and `settings.maintenance_window` to ensure instances are eligible for updates. (Supported: true, Latest Version: 5.0+, First Version: 4.0+, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))

*   **Cloud SQL for MySQL - Updated Time Zone Rules**
    *   **Feature & Security Summary**: Similar to PostgreSQL, this update details a correction to Cloud SQL for MySQL's internal time zone rules to accurately reflect permanent standard daylight offsets across Alberta, British Columbia, Manitoba, and Northwest Territories. This is crucial for maintaining data integrity and preventing discrepancies in time-sensitive operations, which could impact compliance, reporting, and application logic. The updated rules are supported in Cloud SQL for MySQL maintenance release `*.R20260726.00_36` or later. An alternative mitigation involves configuring the `default_time_zone` database flag to a fixed numeric offset, which can be applied without an instance restart, though applying the maintenance release is the recommended long-term solution for comprehensive accuracy.
    *   **Terraform Availability**: Cloud SQL for MySQL instances are managed using the `google_sql_database_instance` resource. The `settings.database_flags` argument can be used to configure the `default_time_zone` flag if the alternative mitigation is chosen. Maintenance windows can also be managed via `settings.maintenance_window`. (Supported: true, Latest Version: 4.80.0, First Version: 1.0.0, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))

*   **Cloud SQL for SQL Server - Time Zone Lag Resolution**
    *   **Feature & Security Summary**: This announcement addresses a critical operational issue where Cloud SQL for SQL Server instances configured with specific Canadian time zones (Pacific Standard Time, Mountain Standard Time, Central Standard Time) would incorrectly observe a one-hour lag after November 1, 2026. This issue could lead to significant data integrity problems, incorrect scheduling, and compliance failures for applications relying on accurate timestamps. The recommended fix involves updating the instance's time zone setting to a corresponding Windows time zone with a fixed UTC offset (e.g., 'Pacific Standard Time' to 'Yukon Standard Time' for British Columbia). This proactive measure ensures precise timekeeping, preventing data corruption and maintaining the reliability of time-sensitive operations and audit trails.
    *   **Terraform Availability**: Cloud SQL for SQL Server instances are managed by the `google_sql_database_instance` resource. The `settings.time_zone` argument within this resource can be used to configure the instance's time zone, allowing for the recommended fix to be applied via IaC. (Supported: true, Latest Version: 5.0.0, First Version: 1.0.0, Resource: `google_sql_database_instance`, Provider Doc: [https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance))

### AlloyDB for PostgreSQL
**Feature & Security Summary:** The enhancement improves operational experience for Advanced Query Insights on AlloyDB for PostgreSQL. For clusters running PostgreSQL 18 or newer, modifications to settings such as `query_string_length` and enabling active query analysis can now be performed without requiring an instance restart. This change reduces downtime, increases administrative agility, and maintains strong observability for query performance and security analysis. For clusters on PostgreSQL 17 or earlier, a restart is still required. The feature strengthens compliance and security posture by enabling faster tuning of query insights without interrupting workloads. **Terraform Availability:** Supported in the HashiCorp Google Terraform Provider (`hashicorp/google`) via `google_alloydb_cluster` resource (query_insights_config block) since version 4.30.0. [Provider Documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/alloydb_cluster#query_insights_config)

## Announcements in this summary

- [BigQuery](https://docs.cloud.google.com/release-notes?product=bigquery#October_30_2026) (Analytics)
- [Apigee hybrid](https://docs.cloud.google.com/release-notes?product=apigee-hybrid#October_30_2026) (API Management)
- [Google Cloud SQL](https://docs.cloud.google.com/release-notes?product=backup-and-dr#October_30_2026) (Databases)
- [Cloud Run](https://docs.cloud.google.com/release-notes?product=cloud-run#October_30_2026) (Compute)
- [Google Cloud Bigtable](https://docs.cloud.google.com/release-notes?product=bigtable#October_30_2026) (Databases)
- [Cloud SQL for PostgreSQL](https://docs.cloud.google.com/release-notes?product=cloud-sql-for-postgresql#October_30_2026) (Database)
- [Cloud SQL for MySQL](https://docs.cloud.google.com/release-notes?product=cloud-sql-for-mysql#October_30_2026) (Databases)
- [Cloud SQL for SQL Server](https://docs.cloud.google.com/release-notes?product=cloud-sql-for-sql-server#October_30_2026) (Databases)
- [AlloyDB for PostgreSQL](https://docs.cloud.google.com/release-notes?product=alloydb-for-postgresql#October_30_2026) (Databases)
