"title"=>"March 21, 2024",
"summary"=>nil,
"content"=>"Anthos Config Management\n
Feature
\nThe constraint template library includes a new template: K8sPSSRunAsNonRoot
. For reference, see the Constraint template library.
Changed
\nPolicy Controller bundles have been updated to the following versions: cis-gke-v1.4.0
: 202402.0-preview
, nist-sp-800-190
: 202402.0
, nist-sp-800-53-r5
: 202402.0
, pci-dss-v3.2.1
: 202402.0
, pss-baseline-v2022
: 202402.0
, pss-restricted-v2022
: 202402.0
. For reference, see Policy Controller bundles overview.
Fixed
\nFixed a regression introduced in 1.16.0 that limits the length of the Secret name referenced in the spec.git.secretRef.name
field of the RootSync object.
Fixed
\nFixed a regression introduced in 1.17.0 that caused Config Sync to sometimes fail to pull the latest commit from a Git branch by upgrading git-sync (Config Sync dependency for pulling from git) from v4.1.0 to v4.2.1.
\nBackup and DR\nAnnouncement
\nBackup and DR Service 11.0.10.417 is now available to update your backup/recovery appliance. Refer to these instructions to update your appliance.
\nAnnouncement
\nBackup and DR Service 11.0.10 includes an operating system upgrade from CentOS 7 to Rocky Linux 8. As CentOS 7 will reach its End of Life (EOL) on June 24, 2024, you must upgrade to 11.0.10 before the EOL date to continue receiving security updates.
\n\nTo upgrade to 11.0.10, you should take a snapshot of the appliance's boot disk. If your backup/recovery appliance is on 11.0.5 or below, then you need to upgrade to 11.0.9 before successfully upgrading to 11.0.10. See 11.0.9 release notes to know how to back up the boot disk.
\nFeature
\nBackup and DR Service added support to access historical reports. Learn more.
\nBigQuery\nFeature
\nYou can now add Salesforce Data Cloud data to BigQuery. This feature is generally available (GA).
\nFeature
\nIncremental materialized views now support LEFT OUTER JOIN
and UNION ALL
. This feature is in preview.
Feature
\nYou can now view Bigtable cost data with instance granularity in the Google Cloud Billing detailed export to BigQuery. For more information, see Structure of detailed cost data export.
\nCompute Engine\nFeature
\nGenerally available: In a managed instance group (MIG), you can set metadata and labels for all VMs in the group without the need to create a new instance template. For more information, see Override instance template properties with an all-instances configuration.
\nFeature
\nGenerally available: In a managed instance group (MIG), you can turn off repairs to inspect failed and unhealthy VMs, to implement your own repair logic, or to monitor the application health without triggering repairs by MIG. For more information, see Turn off repairs in a MIG.
\nDataproc\nAnnouncement
\nNew Dataproc on Compute Engine subminor image versions:
\n\n- \n
- 2.0.96-debian10, 2.0.96-rocky8, 2.0.96-ubuntu18 \n
- 2.1.44-debian11, 2.1.44-rocky8, 2.1.44-ubuntu20, 2.1.44-ubuntu20-arm \n
- 2.2.10-debian12, 2.2.10-rocky9, 2.2.10-ubuntu22 \n
Announcement
\nRelease 1.28.300-gke.131
\n\nGKE on Bare Metal 1.28.300-gke.131 is now available for download. To upgrade, see Upgrade clusters. GKE on Bare Metal 1.28.300-gke.131 runs on Kubernetes 1.28.
\n\nIf you use a third-party storage vendor, check the GDCV Ready storage partners document to make sure the storage vendor has already passed the qualification for this release of GKE on Bare Metal.
\nChanged
\nFunctionality changes:
\n\n- \n
Updated preflight checks to add a check for networking kernel modules.
\nUpdated preflight checks to remove the check for
iptables
package availability. \nIncreased the default memory limit for
node-exporter
. \n
Fixed
\nFixes:
\n\n- \n
- Fixed an issue with configuring a proxy for your cluster that required you to manually set
HTTPS_PROXY
andNO_PROXY
environment variables on the admin workstation. \n
Fixed
\nThe following container image security vulnerabilities have been fixed in 1.28.300-gke.131:
\n\n- \n
High-severity container vulnerabilities:
\n\n \nMedium-severity container vulnerabilities:
\n\n \nLow-severity container vulnerabilities:
\n\n \n
Issue
\nKnown issues:
\n\nFor information about the latest known issues, see GKE on Bare Metal known issues in the Troubleshooting section.
\nAnnouncement
\nRelease 1.15.11
\n\nGKE on Bare Metal 1.15.11 is now available for download. To upgrade, see Upgrade clusters. GKE on Bare Metal 1.15.11 runs on Kubernetes 1.26.
\n\nIf you use a third-party storage vendor, check the GDCV Ready storage partners document to make sure the storage vendor has already passed the qualification for this release of GKE on Bare Metal.
\nFixed
\nThe following container image security vulnerabilities have been fixed in 1.15.11:
\n\n- \n
Medium-severity container vulnerabilities:
\n\n \nLow-severity container vulnerabilities:
\n\n- \n
- CVE-2021-25743 \n
\n
Issue
\nKnown issues:
\n\nFor information about the latest known issues, see GKE on Bare Metal known issues in the Troubleshooting section.
\nGoogle Distributed Cloud Virtual for VMware\nAnnouncement
\nGKE on VMware 1.28.300-gke.123 is now available. To upgrade, see\nUpgrading GKE on VMware.\nGKE on VMware 1.28.300-gke.123 runs on Kubernetes v1.28.4-gke.1400.
\n\nIf you are using a third-party storage vendor, check the\nGDCV Ready storage partners\ndocument to make sure the storage vendor has already passed the qualification\nfor this release of GKE on VMware.
\nChanged
\n- \n
- Increased the default memory limit for node-exporter. \n
- Updated the AIS version to hybrid_identity_charon_20240228_0730_RC00. \n
Fixed
\nThe following issues are fixed in 1.28.300-gke.123:
\n\n- \n
- Fixed the issue where the admin cluster backup did a retry on\nnon-idempotent operations. \n
- Fixed the\nknown issue\nwhere the
controlPlaneNodePort
field defaulted to 30968 when the manualLB\nspec was empty. \n - Fixed the\nknown issue\nthat caused the preflight check to fail when the hostname wasn't in the IP\nblock file. \n
- Fixed the\nknown issue\nthat caused Kubelet to be flooded with logs stating that\n"/etc/kubernetes/manifests" does not exist on the worker nodes. \n
The following vulnerabilities are fixed in 1.28.300-gke.123:
\n\n- \n
High-severity container vulnerabilities:
\n\n \nContainer-optimized OS vulnerabilities:
\n\n- \n
- CVE-2023-40547 \n
\n
Feature
\nSecurity Command Center detectors are now mapped to the following additional compliance frameworks:
\n\n- \n
- CIS Critical Security Controls v8 \n
- Cloud Controls Matrix v 4 \n
- HIPAA \n
- ISO 27001 (2022) \n
- NIST 800-53 (rev 5) \n
- NIST Cybersecurity Framework (v 1.0) \n
- PCI-DSS 4.0 \n
- SOC 2 (2017) \n
Feature
\nPreview stage support for the following integration:
\n\n\nreCAPTCHA Enterprise\nFeature
\nreCAPTCHA Enterprise platform logs are now available in Chronicle. Users can now view their reCAPTCHA assessment and annotation data in a structured and searchable data format in Chronicle. For more information, see Collect reCAPTCHA Enterprise logs.
\n\n ","author"=>nil,
"link"=>"https://cloud.google.com/release-notes#March_21_2024",
"published_date"=>Thu, 21 Mar 2024 07:00:00.000000000 UTC +00:00,
"image_url"=>nil,
"feed_url"=>"https://cloud.google.com/release-notes#March_21_2024",
"language"=>nil,
"active"=>true,
"ricc_source"=>"feedjira::v1",
"created_at"=>Sun, 31 Mar 2024 21:42:30.533795000 UTC +00:00,
"updated_at"=>Mon, 13 May 2024 18:40:08.368428000 UTC +00:00,
"newspaper"=>"GCP latest releases",
"macro_region"=>"Technology"}