"title"=>"February 28, 2024",
"summary"=>nil,
"content"=>"AlloyDB for PostgreSQL\n
Feature
\nAlloyDB now supports the use of Google Cloud tags on cluster and backup resources. Tags are key-value pairs you can apply to your resources for granular IAM permissions. To learn more, see Organize resources using tags. To use tags now, see Attach and manage tags on AlloyDB resources.
\nAnti Money Laundering AI\nAnnouncement
\nAdded a new engine version page so you can keep track of the latest engine version releases.
\nBackup and DR\nFeature
\nBackup and DR Service is now integrated with Cloud Monitoring. You can analyze metrics and set custom email alerts. Learn more.
\nFeature
\nBackup and DR Service has added a new reporting system based on the built-in Google Cloud services: Cloud Monitoring, Cloud Logging, and BigQuery. Learn more.
\nFeature
\nYou can now view prebuilt reports in BigQuery. Learn more.
\nFeature
\nYou can now view comprehensive job related reporting data through backup and recovery job logs in Cloud Logging. Learn more.
\nBigQuery\nFeature
\nMaterialized views can now reference logical views. This feature is in preview.
\nFeature
\nThe ability to perform\nanomaly detection\nwith BigQuery ML\nmultivariate time series (ARIMA_PLUS_XREG) models\nis now in\npreview.\nThis feature enables you to detect anomalies in historical time series data or\nin new data with multiple feature columns. Try this new feature by using the\nPerform anomaly detection with a multivariate time-series forecasting model\ntutorial.
Feature
\nThe following statements are now generally available (GA) with billing enabled:
\n\n- \n
CREATE TABLE AS SELECT\nCREATE TABLE IF NOT EXISTS AS SELECT\nCREATE OR REPLACE TABLE AS SELECT\nINSERT INTO SELECT\n
These statements let you filter data from files in Amazon S3 and Azure Blob Storage before transferring results into BigQuery tables.
\nCloud Composer\nAnnouncement
\nCloud Composer 2.6.3 release started on February 28, 2024. Get ready for upcoming changes and features as we roll out the new release to all regions. This release is in progress at the moment. Listed changes and features might not be available in some regions yet
\nChanged
\n(Cloud Composer 2 in select regions) Cloud Composer shows the account selection and consent screens when opening Airflow UI for an environment.
\n\nIf you have the "Don't allow users to access any third-party apps" setting enabled in Google Workspace, then configure access to the "Apache Airflow in Cloud Composer" app in Google Workspace, so that your Google Workspace users can still access Airflow UI in Cloud Composer environments. For more information, see Allow access to Airflow UI in Google Workspace.
\nChanged
\n(Cloud Composer 2 in select regions) Reduced the propagation time of the revoked Cloud IAM permission that blocks access to Airflow UI.
\nChanged
\nIn new environments with Airflow 2.6.3, the default values of the following Airflow configuration options are changed to provide more optimized Cloud Composer environments:
\n\n- \n
[scheduler]job_heartbeat_secto30\n[scheduler]scheduler_heartbeat_secto15\n
Fixed
\nFixed a problem where the IAM policy of a custom environment's bucket is replaced when an environment is created.
\nChanged
\nThe apache-airflow-providers-google package is upgraded to version 10.15.0 in images with Airflow 2.6.3. For more information about changes, see the apache-airflow-providers-google changelog from version 10.14.0 to version 10.15.0.
Changed
\nCloud Composer 2.6.3 images are available:
\n\n- \n
- composer-2.6.3-airflow-2.6.3 (default) \n
- composer-2.6.3-airflow-2.5.3 \n
Feature
\nData collaborators can now check if memory monitoring is enabled on a Confidential VM running a Confidential Space workload.
\nAnnouncement
\nA new Confidential Space image (240200) is now available. This image provides support for data collaborators to add memory monitoring as part of their attestation assertions.
\nDataproc\nAnnouncement
\nNew Dataproc on Compute Engine subminor image versions:
\n\n- \n
- 2.0.93-debian10, 2.0.93-rocky8, 2.0.93-ubuntu18 \n
- 2.1.41-debian11, 2.1.41-rocky8, 2.1.41-ubuntu20, 2.1.41-ubuntu20-arm \n
- 2.2.7-debian12, 2.2.7-rocky9, 2.2.7-ubuntu22 \n
Feature
\nDataproc on Compute Engine: The new Secret Manager credential provider feature is available in the latest 2.1 image versions.
\nChanged
\nDataproc on Compute Engine:
\n\n- \n
- Upgraded Zookeeper to 3.8.3 for Dataproc 2.2. \n
- Upgraded ORC for Hive to 1.15.13 for Dataproc 2.1. \n
- Upgraded ORC for Spark to 1.7.10 for Dataproc 2.1. \n
- Extended expiry for the internal Knox Gateway certificate from one year to five years from cluster creation for Dataproc images 2.0, 2.1, and 2.2. \n
Fixed
\nDataproc on Compute Engine: Fixed ZooKeeper startup failures in image 2.2 HA (High Availability) clusters that use fully qualified hostnames.
\nDeep Learning VM Images\nFeature
\nM117 release
\n\n- \n
- Added the CUDA version (CUDA 11.8) to the TensorFlow 2.12, 2.13, and 2.14 image names and image family names. For example,
tf-2-12-gpuis renamedtf-2-12-cu118. \n
Feature
\n(New guide) Configure networks for FedRAMP and DoD in Google Cloud: Provides configuration guidance to help you comply with design requirements for FedRAMP High and DoD IL2, IL4, and IL5 when you deploy Google Cloud networking policies.
\nFeature
\n(New guide) Infrastructure for a RAG-capable generative AI application using Vertex AI: Design infrastructure to run a generative AI application with retrieval-augmented generation (RAG) to help improve the factual accuracy and contextual relevance of LLM-generated content.
\nGoogle Cloud VMware Engine\nAnnouncement
\nBeginning on March 12, 2024, the VMware Engine operations team will perform essential maintenance of the network infrastructure to improve equipment robustness and apply security patches. Users affected by this upgrade will receive an email with planned maintenance dates and times.
\n\nFor details about the upgrade and steps to prepare, see Service annoucements.
\nGoogle Kubernetes Engine\nFeature
\nThe Performance Compute Class, designed for running whole-machine CPU workloads, is available in Autopilot mode from versions 1.28.6-gke.1369000 and 1.29.1-gke.1575000 and later.
\nSAP on Google Cloud\nFeature
\nDisk snapshot based backup and recovery for SAP HANA
\n\nFrom version 3.0, you can use the disk snapshot feature of Google Cloud's Agent for SAP to perform backup and recovery operations for SAP HANA systems running on Google Cloud.
\n\nFor more information, see Disk snapshot based backup and recovery for SAP HANA.
\nSecurity Command Center\nFeature
\nVirtual Machine Threat Detection, a built-in service of Security Command Center Premium, has launched a new detector, Defense Evasion: Rootkit, in Preview.
The detector monitors virtual machines and generates a finding if a combination of signals matching a known kernel-mode rootkit is present.
\n\nFor more information, see Virtual Machine Threat Detection overview.
\nVertex AI Search and Conversation\nFeature
\nVertex AI Search: Add metadata to your web index (Public preview)
\n\nIf advanced website indexing is enabled in your data store, you can add metadata to the data store schema to enrich your indexing.
\n\nFor more information, see Add metadata for advanced site indexing.
\nFeature
\nVertex AI Search: Automatic web page refresh (Public preview)
\n\nWith advanced website indexing, Vertex AI Search performs conditional, automatic refresh.
\n\nFor more information, see Refresh web pages.
\nFeature
\nVertex AI Search: Apply tuned search to some queries (Public preview)
\n\nYou can specify whether you want a query to use the tuned search model or the non-tuned search model. This is particularly helpful for testing the difference between the two versions of the model.
\n\nPreviously, the tuned search model was enabled (or disabled) for all queries against the data store.
\n\nFor more information, see Test tuned search and use it for individual search queries.
\nFeature
\nVertex AI Search: Access controlled data sources (Public preview)
\n\nAccess control for BigQuery, Cloud Storage, and Confluence data is available in Public preview. This feature allows you to limit the data that users can view in your search app's results. Google uses your identity provider to identify the end user performing a search and determine if they have access to the documents that are returned as results. Google Identity and third-party identity provider federation are supported.
\n\nFor more information, seeย Use data source access control.
\nFeature
\nVertex AI Search: Blended search (Public preview)
\n\nBlended search, where multiple data stores can be connected to a single generic search app, is available in Public preview. This feature allows you to use one generic search app to search across multiple sources and types of data.
\n\nFor more information, seeย About connecting multiple data stores.
\nFeature
\nVertex AI Search: Search analytics (GA)
\n\nSearch analytics are GA for global data stores. For data stores in US and EU multi-regions, viewing analytics is in Public Preview.
\n\nFor more information, see View analytics.
\nVertex AI Workbench\nFeature
\nM117 release
\n\nThe M117 release of Vertex AI Workbench instances includes the following:
\n\n- \n
- Removed the Cloud Storage browser in the left side pane in favor of the existing Mount shared storage button. \n
"author"=>nil,
"link"=>"https://cloud.google.com/release-notes#February_28_2024",
"published_date"=>Wed, 28 Feb 2024 08:00:00.000000000 UTC +00:00,
"image_url"=>nil,
"feed_url"=>"https://cloud.google.com/release-notes#February_28_2024",
"language"=>nil,
"active"=>true,
"ricc_source"=>"feedjira::v1",
"created_at"=>Sun, 31 Mar 2024 21:42:29.859595000 UTC +00:00,
"updated_at"=>Mon, 13 May 2024 18:44:13.030633000 UTC +00:00,
"newspaper"=>"GCP latest releases",
"macro_region"=>"Technology"}