Real-time pre-release intelligence and changelog for Google AlloyDB. Tracked from Google Discovery Service.https://google-cloud-radar.com/en-ushttps://google-cloud-radar.com/changes/2026-11-02-alloydb-v1https://google-cloud-radar.com/changes/2026-11-02-alloydb-v1AlloyDB's autoscaling policies for read pools can now leverage connection count as a scaling metric. This allows for more granular control, enabling dynamic adjustments based on the number of active database connections.Mon, 02 Nov 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1mediumfalse7canaryhttps://google-cloud-radar.com/changes/2026-11-01-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-11-01-alloydb-v1betaAlloyDB v1beta now introduces a new autoscaling policy type based on connection count. You can configure your autoscaler to scale instances based on a target number of connections.Sun, 01 Nov 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betamediumfalse7canaryhttps://google-cloud-radar.com/changes/2026-11-01-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-11-01-alloydb-v1alphaAlloyDB introduces a new `connectionsCount` policy for autoscaling, allowing you to scale instances based on the target number of active connections. This provides finer-grained control over resource allocation.Sun, 01 Nov 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphamediumfalse7canaryhttps://google-cloud-radar.com/changes/2026-10-22-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-10-22-alloydb-v1betaAlloyDB v1beta now exposes cluster Certificate Authority (CA) details and instance network information as read-only properties. Developers should note that several new fields, including CA certificates and instance network details, are now explicitly output-only, which is a breaking change if you were attempting to set them.Thu, 22 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betamediumtrue8canaryhttps://google-cloud-radar.com/changes/2026-10-22-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-10-22-alloydb-v1alphaAlloyDB now provides crucial CA certificate information for secure PostgreSQL connections and public DNS names for instances. A new `publicDnsEnabled` option allows configuring public DNS. Be aware of breaking changes as `rootCaCert`, `certificateAuthorityInfo`, `networkInfo`, and `publicDnsName` are now read-only.Thu, 22 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphahightrue8canaryhttps://google-cloud-radar.com/changes/2026-10-13-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-10-13-alloydb-v1betaThe recently introduced `edition` field on AlloyDB `Cluster` and `Backup` schemas is now deprecated. Developers should transition to using the new `expressConfig` property on `Backup` for Express cluster details, which is output-only and considered a breaking change if you anticipated setting it.Tue, 13 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betahightrue9canaryhttps://google-cloud-radar.com/changes/2026-10-13-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-10-13-alloydb-v1alphaThe `edition` field on both `Backup` and `Cluster` resources is now deprecated, with a recommendation to use the `ExpressConfig` property instead. Additionally, the `expressConfig` property on `Backup` has been made read-only, which is a breaking change if you were previously setting it.Tue, 13 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphahightrue8canaryhttps://google-cloud-radar.com/changes/2026-10-13-alloydb-v1https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1AlloyDB now supports autoscaling for read pools, allowing you to dynamically adjust the number of read replica nodes based on CPU utilization or predefined schedules. This significantly simplifies managing read capacity and optimizing costs.Tue, 13 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1highfalse9canaryhttps://google-cloud-radar.com/changes/2026-10-02-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-10-02-alloydb-v1betaAlloyDB v1beta now supports Express clusters via a new `expressConfig` property on the `Cluster` schema. Developers should note significant breaking changes: several observability and query insights properties on `Instance` and related schemas are now read-only.Fri, 02 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betahightrue9canaryhttps://google-cloud-radar.com/changes/2026-10-02-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-10-02-alloydb-v1alphaAlloyDB v1alpha now supports creating Express clusters. Be aware of breaking changes: several observability and query insights fields on `Instance` are now read-only, becoming output-only information.Fri, 02 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphahightrue9canaryhttps://google-cloud-radar.com/changes/2026-10-02-alloydb-v1https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1AlloyDB instances now expose `observabilityInstanceInfo` and `queryInsightsInfo` as output-only fields. Any existing code attempting to modify these properties will now encounter errors, as they are strictly immutable. Update your integrations to treat these as informational.Fri, 02 Oct 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1hightrue8releasedhttps://google-cloud-radar.com/changes/2026-09-25-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-09-25-alloydb-v1betaThe `trackActiveQueryPlan` property within AlloyDB's `ObservabilityInstanceConfig` schema has been deprecated. Developers should plan to migrate away from using this feature.Fri, 25 Sep 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betamediumfalse6canaryhttps://google-cloud-radar.com/changes/2026-09-25-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-09-25-alloydb-v1alphaThe `trackActiveQueryPlan` field within the `ObservabilityInstanceConfig` schema has been marked as deprecated. Developers should update their configurations to avoid using this field.Fri, 25 Sep 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphamediumfalse6canaryhttps://google-cloud-radar.com/changes/2026-09-25-alloydb-v1https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1AlloyDB now supports new `userType` enum values for IAM group-based authentication, enabling more flexible and granular control over database access for groups, users, and service accounts.Fri, 25 Sep 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1highfalse8canaryhttps://google-cloud-radar.com/changes/2026-09-18-alloydb-v1betahttps://google-cloud-radar.com/changes/2026-09-18-alloydb-v1betaAlloyDB v1beta introduces support for PostgreSQL 19 and a new Edition classification for clusters, including a Developer edition. Note that the edition field on Backups is now read-only.Fri, 18 Sep 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1betahightrue8canaryhttps://google-cloud-radar.com/changes/2026-09-18-alloydb-v1alphahttps://google-cloud-radar.com/changes/2026-09-18-alloydb-v1alphaAlloyDB v1alpha introduces support for Postgres 19 and a new edition classification for clusters, while making the edition field read-only on backups.Fri, 18 Sep 2026 00:00:00 GMTDatabasesAlloyDBalloydb.v1alphamediumtrue7canary