Google Distributed Cloud for bare metal 1.31.100-gke.136 is now available for download

## Announcement ### Release 1.31.100-gke.136 Google Distributed Cloud for bare metal 1.31.100-gke.136 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.31.100-gke.136 runs on Kubernetes 1.31. 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. ## Feature The following feature is available in 1.31.100-gke.136: * **GA:** Added [bmctl configure projects](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/reference/bmctl#configure%5Fprojects) command to automatically configure IAM policy bindings for [workload identity cluster authentication](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/keyless). Creates required service accounts and enables required APIs. ## Change The following functional change was made in 1.31.100-gke.136: * Cluster deletion now deletes worker node pools prior to deleting any control plane node pools. ## Fix The following issues are fixed in 1.31.100-gke.136: * Fixed [an issue](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/troubleshooting/known-issues#immutable-field-error-when-updating-user-clusters-with-bmctl-version-1.30.x) where `bmctl update cluster`command fails for user clusters that were created with the`cloudOperationsServiceAccountKeyPath` setting in the header section of the cluster configuration file. * Fixed an issue where prompting during `bmctl update cluster` prevented use of automation. You can now use the `--quiet` flag to skip prompting. * Fixed an issue where node machines didn't update when the registry mirror `hosts` field was updated. ## Fix The 1.31.100-gke.136 release includes many vulnerability fixes. For a list of all vulnerabilities fixed in this release, see [Vulnerability fixes](https://cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/vulnerabilities). ## Issue 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.