Google Distributed Cloud for bare metal 1.30.300-gke.84 is now available for download

## Announcement ### Release 1.30.300-gke.84 Google Distributed Cloud for bare metal 1.30.300-gke.84 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.300-gke.84 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. ## 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 an issue where the registry mirror reachability check fails for a single unreachable registry mirror. Now the reachability check applies to configured registry mirrors only, instead of all registry mirrors. ## Fix The following container image security vulnerabilities have been fixed in 1.30.300-gke.84: * Low-severity container vulnerabilities: * [CVE-2024-43167](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43167) * [CVE-2024-43168](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43168) ## 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.