🚀 Autobase 2.11 - Full PostgreSQL lifecycle management
Autobase 2.11 is an important milestone in the evolution of the platform. Two years ago, we started working on a broader goal: evolve the Autobase Console from a PostgreSQL deployment UI into a platform for managing the complete cluster lifecycle.
With this release, the remaining major pieces of that roadmap are now in place - scaling, upgrades, backups, and point-in-time recovery can all be managed directly from the Platform UI.
This completes the original Cluster management functionality roadmap, but there is much more ahead. Upcoming releases will bring major capabilities such as built-in monitoring, RBAC, and sharding - enabling horizontal scaling beyond the write and storage limits of a single PostgreSQL primary for very high-load workloads.
Stay tuned for the next Autobase releases 📈
✨ Highlights
Autobase Enterprise can now manage the PostgreSQL cluster lifecycle from a single control plane - from deployment and configuration to scaling, upgrades, backup, recovery, and day-2 operations.
Scaling (read replicas)
Scale PostgreSQL read capacity directly from the UI. Simply specify the desired number of cluster nodes, and Autobase will provision the additional replicas automatically using the existing cloud configuration.
For cloud deployments, the required servers and related infrastructure resources are created automatically. You can also scale clusters running on your own bare-metal or virtual machines.
Start with a single-node PostgreSQL cluster and add replicas later as your workload grows.
Upgrades
Autobase Platform now supports minor upgrades within the current PostgreSQL major version as well as major-version upgrade workflows.
For minor upgrades, replicas are updated one at a time, followed by a switchover and upgrade of the former primary. Read traffic remains available throughout the process, while expected write downtime is only ~5-10 seconds.
For in-place major upgrades, the expected downtime is typically ~30-60 seconds. A blue-green major upgrade workflow with near-zero downtime is planned for a future release.
Backup & Restore (PITR)
Backup and recovery management is now available directly in the Platform UI. Configure the backup method, storage, retention, and schedule, or create backups on demand.
Restore options include:
- Latest — recover to the latest available state
- Point in time — restore to a specific date and time
- Specific backup — restore from a selected backup
New Ansible playbooks
Autobase 2.11 adds new Ansible playbooks for backup and recovery operations:
enable_backups— enable pgBackRest or WAL-G for an existing clusterbackup_pgcluster— create a backup on demandbackup_list— list available backupsrestore_pgcluster— restore a PostgreSQL cluster from backup
What's Changed
- Bump fast-uri from 3.1.4 to 3.1.5 in /console/ui by @dependabot[bot] in #1640
- Run bind_address role only if undefined by @vitabaks in #1641
- Remove stop-auto pgbackrest option by @vitabaks in #1642
- Update npm dependencies by @renovate[bot] in #1645
- Update go dependencies by @renovate[bot] in #1644
- Add pgBackRest incremental backup cron by @vitabaks in #1646
- Automate postgresql_restore_command variable by @vitabaks in #1648
- Update ansible to version 14 (major) by @renovate[bot] in #1647
- Automate pgBackRest restore command by @vitabaks in #1649
- Automate WAL-G restore command by @vitabaks in #1650
- Add backup_list.yml playbook by @vitabaks in #1651
- Add backup_pgcluster playbook by @vitabaks in #1655
- Add restore_pgcluster playbook by @vitabaks in #1656
- Console: Fix stale data on the Operations page by @vitabaks in #1657
- Do not enable sudo access for postgres by default by @vitabaks in #1658
- fix: Fetch passwords before cluster update by @vitabaks in #1659
- fix: Fetch passwords before PG upgrade by @vitabaks in #1660
- Console: Add Upgrade to Enterprise button by @vitabaks in #1661
- fix problem with host identification in /etc/hosts by @illmouse in #1663
- Console: Add SSH private key validation by @vitabaks in #1664
- cloud_resources: Limit Consul servers to first 7 instances by @vitabaks in #1665
- Update golang Docker tag to v1.27 by @renovate[bot] in #1668
- Wait for AWS NLB creation and add retries by @vitabaks in #1669
- fix: require console auth for the embedded SQL editor (/dbdesk) by @himanshu-ntml in #1671
- Console: Improve SQL editor loading with gzip compression by @vitabaks in #1673
- console/ui: validate the token via API instead of embedding it in the build by @himanshu-ntml in #1672
- Add support for upgrading a single-node cluster by @vitabaks in #1670
- Fix TLS certificate regeneration during cluster scaling by @vitabaks in #1676
- Fix Patroni replication lag units in Console by @vitabaks in #1677
- pgbackrest: add pgbackrest_repo_external to skip the [pgbackrest] group requirement by @fasiihullah in #1675
- Console: Show missing required fields in the cluster creation form by @vitabaks in #1678
- Console: Add backup defaults and apply in forms by @vitabaks in #1679
- Fix role tag handling in deployment playbooks by @vitabaks in #1680
- Bump fast-uri from 3.1.5 to 3.1.7 in /console/ui by @dependabot[bot] in #1682
- Bump @faker-js/faker from 9.9.0 to 10.5.0 in /console/ui by @dependabot[bot] in #1683
- Bump browserslist from 4.28.1 to 4.28.8 in /console/ui by @dependabot[bot] in #1686
- Update go dependencies by @renovate[bot] in #1667
- Add enable_backups playbook by @vitabaks in #1681
- Fix Azure backup credentials when updating configuration by @vitabaks in #1687
- fix(update): transfer etcd leadership before reboot by @pat-s in #1685
- Add custom cloud resource tagging support by @vitabaks in #1688
New Contributors
- @himanshu-ntml made their first contribution in #1671
Full Changelog: 2.10.0...2.11.0
Ready to try?
Follow the Getting Started guide to deploy the Autobase Platform and create your first PostgreSQL cluster.
You can run PostgreSQL on your own bare-metal or virtual machines, or let Autobase provision the required infrastructure in a supported cloud provider.
