Dear Customer,
we are going to update the a9s platform during the scheduled timeframe.
Runtime
Buildpacks: Changed defaults and removed runtime versions
The Go buildpack updates from v1.11.0 to v1.11.2. Its default Go version changes from 1.25.x to 1.26.x.
Action required: Test applications that rely on the default Go version before restaging. Review explicitly pinned runtime versions against the updated buildpacks. Python 3.12.10 is removed from the Python buildpack.
See the Go buildpack v1.11.1 release notes and Python buildpack v1.9.8 release notes.
Data Services (e.g. removal, deprecation, unsupported, new services)
a9s PostgreSQL 15 and 17: Cluster sync on update
anynines-deployment v78.0.0 enables temporary synchronous replication during primary-node updates for healthy clusters with at least three nodes. This also applies to the PostgreSQL 15 cluster in a9s-pg. Existing clusters use the feature from the first update after they run the new release.
Writes can take longer while the cluster is synchronous, particularly when the remaining standby is busy with backups or long-running queries. See operator information for requirements, configuration and mitigation.
a9s Search and a9s LogMe2: Snapshot backup reporting and downloads
anynines-deployment v78.0.0 removes the non-functional manual backup download button from the Service Dashboard. Creating, listing and restoring backups remains supported. These backups are OpenSearch snapshots written directly to backup storage, not a single downloadable file.
a9s Search reports the actual size of new snapshot backups. Existing backups keep their previously reported size of 0 B. See the v78.0.0 changelog.
Planned Ubuntu 24.04 ("Noble Numbat") stemcell rollout
This is advance notice from anynines-deployment v78.0.0, not an instruction to move existing Data Service instances to Noble with this update.
The supported migration targets listed upstream are a9s MariaDB 10.11, a9s Messaging 4, a9s MongoDB 7 and 8, a9s PostgreSQL 15 and 17, and a9s Search 2.
Unsupported versions are not tested or adapted for Noble: a9s MariaDB 10.4, a9s Messaging 3.7, 3.8, 3.10, 3.12 and 3.13, a9s MongoDB 5, and a9s PostgreSQL 10, 11 and 13. a9s Search 1 is no longer supported and is not expected to work on Noble. Compatibility is being evaluated for a9s MariaDB 10.6 and a9s Prometheus 2; compatibility is not guaranteed.
Action required: Disable plans referencing unsupported templates to prevent new instances. Plan and complete migrations of affected existing instances before moving them to Noble. Follow each service's migration documentation; changing a plan's template is not a supported major-version migration.
See the v78.0.0 upgrade notes. No rollout month is specified there.
The update procedure is structured into 3 stages:
Stage 1: Update of the Runtime
Stage 2: Update of the a9s Data Service Framework
Stage 3: Update of all existing a9s Data Service instances
The stages have the following impact:
Stage 1:
- Restart of all applications. For slow starting applications with a single instance configuration this might introduce a downtime of up to 5 minutes in addition to application startup time.
- Restart of the API. Single requests to the API might fail but subsequent requests shall pass.
Stage 2:
- Creation, update and deletion of new or existing a9s Data Services instances will be unavailable for up to 5 minutes.
- The availability of existing a9s Data Service instances will not be affected by this.
Stage 3:
- All a9s Data Service instances will be restarted which causes single instances to be not available for up to 5 minutes.
- You may see your app reconnecting to the master node while the service instance gets updated.
We'll provide an update as soon as we finish the respective stage.
Best regards,
The anynines Team
Posted Nov 13, 2026 - 15:59 CET