Google Distributed Cloud for bare metal 1.30.200-gke.101 is now available for download
Share
Services
## Announcement
### Release 1.30.200-gke.101
Google Distributed Cloud for bare metal 1.30.200-gke.101 is now available for [download](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/downloads). To upgrade, see [Upgrade clusters](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/upgrade). Google Distributed Cloud for bare metal 1.30.200-gke.101 runs on Kubernetes 1.30.
After a release, it takes approximately 7 to 14 days for the version to become available for installations or upgrades with the [GKE On-Prem API clients](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/cluster-lifecycle-management-tools): the Google Cloud console, the gcloud CLI, and Terraform.
If you use a third-party storage vendor, check the [Ready storage partners](https://cloud.google.com/anthos/docs/resources/partner-storage) document to make sure the storage vendor has already passed the qualification for this release of Google Distributed Cloud for bare metal.
## Change
Updated the `bmctl update` command to identify differences (if any) between the preview feature annotations in the cluster configuration file and the annotations in the deployed Cluster resource.
## Fix
**Fixes:**
* Fixed an issue where the control plane VIP might become unavailable because Keepalived didn't check correctly that the VIP is on a node with a responsive HAProxy.
* Fixed Cloud Audit Logging failure due to allowlisting issue with multiple project IDs.
## Fix
The following container image security vulnerabilities have been fixed in 1.30.200-gke.101:
* Critical container vulnerabilities:
* [CVE-2024-37371](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37371)
* High-severity container vulnerabilities:
* [CVE-2023-47038](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-47038)
* [CVE-2024-0553](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0553)
* [CVE-2024-0567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0567)
* [CVE-2024-37370](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37370)
* [CVE-2024-39487](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39487)
* [CVE-2024-41040](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41040)
* [CVE-2024-41046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41046)
* [CVE-2024-41049](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41049)
* [CVE-2024-41059](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41059)
* [CVE-2024-41070](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41070)
* [CVE-2024-42104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42104)
* [CVE-2024-42148](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42148)
* Medium-severity container vulnerabilities:
* [CVE-2016-3709](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3709)
* [CVE-2023-5981](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-5981)
* [CVE-2024-36901](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36901)
* [CVE-2024-36938](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36938)
* [CVE-2024-41009](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41009)
* [CVE-2024-41012](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41012)
* [CVE-2024-41055](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41055)
* [CVE-2024-41063](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41063)
* [CVE-2024-41064](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41064)
* [CVE-2024-42101](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42101)
* [CVE-2024-42102](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42102)
* [CVE-2024-42131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42131)
* [CVE-2024-42137](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42137)
* [CVE-2024-42152](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42152)
* [CVE-2024-42153](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42153)
* [CVE-2024-42154](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42154)
* [CVE-2024-42157](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42157)
* [CVE-2024-42161](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42161)
* [CVE-2024-42223](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42223)
* [CVE-2024-42224](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42224)
* [CVE-2024-42229](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42229)
* [CVE-2024-42232](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42232)
* [CVE-2024-42236](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42236)
* [CVE-2024-42244](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42244)
* [CVE-2024-42247](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42247)
* [CVE-2024-7264](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7264)
* Low-severity container vulnerabilities:
* [CVE-2022-2309](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2309)
* [CVE-2022-48303](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48303)
* [CVE-2024-41007](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41007)
## Issue
**Known issues:**
For information about the latest known issues, see [Google Distributed Cloud for bare metal known issues](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/troubleshooting/known-issues) in the Troubleshooting section.
What else is happening at Google Cloud Platform?
The CPU allocation setting has been renamed to Billing in the Google Cloud console for Cloud Run services
December 13th, 2024
Services
Share
Google Kubernetes Engine (GKE) - December 13th, 2024 [Feature]
December 13th, 2024
Services
Share