Skip to main content

59.0.0

· 13 min read

Added​

  • breaking change a9s PostgreSQL: We consider PostgreSQL 17 as stable now. You have to set the following properties:
    • postgresql_service.services.a9s-postgresql17.name
    • postgresql_service.services.a9s-postgresql17.guid
    • postgresql_service.services.a9s-postgresql17.description
    • postgresql_service.services.a9s-postgresql17.label
    • postgresql_service.services.a9s-postgresql17.version
    • postgresql_service.services.a9s-postgresql17.bindable
    • postgresql_service.services.a9s-postgresql17.requires
    • postgresql_service.services.a9s-postgresql17.tags
    • postgresql_service.services.a9s-postgresql17.documentation_url
    • postgresql_service.services.a9s-postgresql17.metadata
    • postgresql_service.services.a9s-postgresql17.dashboard_client.id
    • postgresql_service.services.a9s-postgresql17.plans-to-test
    • postgresql_service.services.a9s-postgresql17.planupdates-to-test
  • all services: a9s Bee: Add NGINX as reverse proxy in front of a9s Bee to handle handle TLS termination in the future.
  • all services: a9s BOSH Deployer: Add NGINX as reverse proxy in front of a9s BOSH Deployer to handle TLS termination.
  • all services: a9s Service Broker: Add NGINX as reverse proxy in front of a9s Service Broker to handle TLS termination.
  • all services: a9s SPIs: Add NGINX as reverse proxy in front of a9s SPIs to handle TLS termination.
  • a9s Backup Services: a9s Backup Manager: Extend the response of the Public API v1 endpoint list_backups to return the backup_id, which can be used to specify a backup to restore from, via the Disaster Recovery API or CF Plugin.
  • a9s Backup Services: a9s Backup Manager: Update dependencies.
  • a9s CF Service Guard: Add NGINX as reverse proxy in front of a9s CF Service Guard to handle TLS termination.
  • a9s MariaDB: a9s MariaDB SPI: Introduce reconcile logic to update the value of the default_database attribute in the a9s Service Broker database after restoring an external backup. This enables the Disaster Recovery feature.
  • a9s Prometheus: Introduce a static landing page for the dashboard URL, providing quick access to the following web UIs: Alert Manager, Grafana, and Prometheus.
  • docs: Application Developer: Add a page detailing how Data Service Forking via the Disaster Recovery funcionality works, as there are small but critical differences between them. For more information, see Forking a Service Instancce.
  • docs: Application Developer: all services: Add a "Getting Started" section to host the common functionality from across the a9s Data Services documents. For more information, see Getting Started.
  • docs: Platform Operator: all services: Add a "Getting Started" section to host the overall installation of the a9s Data Services and its framework. For more information, see Getting Started.
  • docs: Platform Operator: a9s PostgreSQL: Add a9s PostgreSQL 17 as a9s General Availability. For more information, see a9s Platform Operator Sunrise Sunset.
  • docs: Platform Operator: a9s PostgreSQL: Add information about the wal_receivers parameter. For more information, see Cluster Status - Status Script.

Changed​

  • all services: Extract the renaming of the a9s Service Broker endpoint for the a9s Service DashboardRefactor from the ops/rename-service-deployment.yml Ops file into the dedicated ops/dashboard-rename-broker-endpoint.yml.
  • all services:
    • a9s DS API Gateway:
      • Update KrakenD to v2.9.3.
      • Update krakend-custom-plugins to v2.9.3.
    • Update bpm to v1.4.16.
    • Update routing to v0.331.0.
  • all services: a9s Backup Agent: Update Ruby to v3.4.1.
  • all services: a9s Backup Agent: Extend the support for special characters when setting the backup encryption key via the a9s Dashboard or the a9s Public API v1.
  • all services: a9s Bee: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of it.
  • all services: a9s BOSH Deployer: Update Ruby to v3.4.1.
  • all services: a9s BOSH Deployer: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of it.
  • all services: a9s CF Service Guard: Update Ruby to v3.4.1.
  • all services: a9s Deployment Updater Errand: Update Ruby to v3.4.1.
  • all services: a9s Logstash: Logstash 6: Update Ruby to v3.4.1.
  • all services: a9s Service Broker: Update Ruby to v3.4.1.
  • all services: a9s Service Broker: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of it.
  • all services: a9s SSO Proxy: Update Ruby to v3.4.1.
  • all services: a9s Smoke Tests: Update Ruby to v3.4.1.
  • all services: a9s SPIs: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of them.
  • all services: a9s SPIs: Update dependencies.
  • all services: a9s Template Uploader Errand: Replace Logstash6 with Logstash8 in the a9s MongoDB templates.
  • all services: a9s Template Uploader Errand: Update Ruby to v3.4.1.
  • a9s-pg: a9s Logstash:
    • Logstash 8:
      • Update logstash8 to v8.17.3.
      • Update Ruby to v3.4.1.
  • a9s Backup Services: a9s Backup Manager: Update Ruby to v3.4.1.
  • a9s Backup Services: a9s Backup Monit: Update Ruby to v3.4.1.
  • a9s Backup Services: a9s Backup Monit: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of it, and adapt the related Logstash configuration accordingly.
  • a9s Backup Services: a9s Backup Monit: Update a9s Backup Manager related configuration to use the TLS encrypted port for communication.
  • a9s CF Service Guard: Change the bind_address property to listen only on localhost, following the introduction of NGINX as reverse proxy in front of it.
  • a9s KeyValue: a9s Logstash:
    • Logstash 8:
      • Update logstash8 to v8.17.3.
      • Update Ruby to v3.4.1.
  • a9s LogMe2:
    • Fluentd:
      • Update Ruby to v3.4.1.
  • a9s MariaDB:
    • MariaDB 10.6: Update Ruby to v3.4.1.
    • MariaDB 10.11: Update Ruby to v3.4.1.
  • a9s Messaging:
    • a9s Logstash:
      • Logstash 8:
        • Update logstash8 to v8.17.3.
        • Update Ruby to v3.4.1.
    • a9s Messaging 4: Update rabbitmq to v4.0.7.
  • a9s MongoDB: Replace Logstash6 with Logstash8.
  • a9s MongoDB:
    • a9s MongoDB 7: Update mongosh to v2.4.2.
  • a9s PostgreSQL:
    • a9s Logstash:
      • Logstash 8:
        • Update logstash8 to v8.17.3.
        • Update Ruby to v3.4.1.
    • a9s PostgreSQL SPI: Update rack to v3.1.12.
    • a9s PostgreSQL 17: Update PostgreSQL to v17.4.
    • a9s PostgreSQL 13: Update PostgreSQL to v3.13.0.
  • a9s Prometheus:
    • prometheus2: Update
      • alertmanager to v0.28.1.
      • blackbox_exporter to v0.26.0.
      • cadvisor to v0.52.1.
      • elasticsearch_exporter to v1.9.0.
      • mysqld_exporter to v0.17.2.
      • postgres_exporter to v0.17.1.
      • prometheus to v2.53.4.
    • prometheus-legacy: Update
      • alertmanager to v0.28.1.
      • blackbox_exporter to v0.26.0.
      • cadvisor to v0.52.1.
      • elasticsearch_exporter to v1.9.0.
      • mysqld_exporter to v0.17.2.
      • postgres_exporter to v0.17.1.
      • prometheus to v2.53.4.
    • promgraf2: Update
      • alertmanager to v0.28.1.
      • blackbox_exporter to v0.26.0.
      • cadvisor to v0.52.1.
      • elasticsearch_exporter to v1.9.0.
      • mysqld_exporter to v0.17.2.
      • postgres_exporter to v0.17.1.
      • prometheus to v2.53.4.
  • a9s Redis: a9s Redis SPI: Update Ruby to v3.4.1.
  • a9s Search: a9s Logstash:
    • Logstash 8: Update
      • logstash8 to v8.17.3.
      • opensearch2 to v2.24.0.
      • Ruby to v3.4.1.
  • docs: Application Developer: Add a9s MariaDB to the list of Data Services that support the Disaster Recovery feature. For more information, see Disaster Recovery.
  • docs: Application Developer: Add backup_id property description to the list_backup endpoint of the Public API V1 with examples of the response. For more information, see API V1 Endpoints - List All Backups.
  • docs: Application Developer: all services: Restructure overall layout and provide more granularity to each a9s Data Services section. For more information, see Application Developer.
  • docs: Application Developer: a9s KeyValue: Reorganize the Custom Parameters page into topics rather than using the parameters themselves as sections. For more information, see Custom Parameters.
  • docs: Application Developer: a9s PostgreSQL: Improve the information regarding a9s PostgreSQL migration caveats.
  • docs: Application Developer: a9s Prometheus: Add information about the newly added index page that enables easier access to the Service Instance's dashboards. For more information, see Service Instance Access.
  • docs: Platform Operator: Add a9s MariaDB to the list of Data Services that support the Disaster Recovery feature. For more information, see Disaster Recovery.
  • docs: Platform Operator: Extend the TLS Encryption with a list of the certificates in use, and a detailed overview of the different use cases for certificate rotation. For more information, see TLS Encryption.
  • docs: Platform Operator: all services: Extend the "Block Automatic Updates" documentation by cross-referencing the individual pages in the a9s Service Broker and a9s Service Dashboard sections. For more information, see a9s Service Broker - Block Automatic Updates and a9s Service Dashboard - Allow Automatic Updates.
  • docs: Platform Operator: all services: Restructure overall layout and provide more granularity to all major components and the general configuration of the a9s Data Services. For more information, see Platform Operator.
  • docs: Platform Operator: a9s Backup Monit: Add link to the Retention Policy section in the a9s Backup Manager Metrics. For more information, see Retention Policy.
  • docs: Platform Operator: a9s Backup Services: Improve the Retention Policy section by adding information about the backup deletion process, fixing typos, and restructuring the section. For more information, see Retention Policy.
  • docs: Platform Operator: a9s PostgreSQL: Add information about resource requirements in face of piled-up WAL files. For more information, see a9s PostgreSQL - Resource Considerations.
  • BOSH stemcell: all services: Update Jammy stemcell to version 1.785 for internal tests of all supported services.

Deprecated​

  • a9s Messaging: Deprecation: Deprecate the following a9s Data Service versions:

    • a9s Messaging 3.12: RabbitMQ 3.12 is end-of-life by their vendor since June 2024
    • a9s Messaging 3.13: RabbitMQ 3.13 is end-of-life by their vendor since Sept 2024

    Please ensure that you organize the migration of your existing Service Instances to a more up-to-date version of the same a9s Data Service:

    • for a9s Messaging 3.12: a9s Messaging 4.0 is available as GA version.
    • for a9s Messaging 3.13: a9s Messaging 4.0 is available as GA version.

    This deprecation follows the announcement in v56.0.0. The deprecation phase is planned to last until v62.0.0 (expected end of June 2024), in which the unsupport phase of the deprecated versions will start. The creation of new a9s Data Service Instances for these particular versions will then be disabled by default in the a9s Data Service Bundle and we will not provide regular support for these versions. The corresponding documentation will also be removed. Therefore, we strongly recommend that you start your migrations to a supported GA version as soon as possible and complete them until the end of the deprecation phase. For more information see a9s Platform Operator - Sunrise Sunset.

    To inquire about extended support for a deprecated version, please get in contact with our sales department at sales@anynines.com.

Unsupported​

  • a9s MySQL: End of Support: Terminate support for the following deprecated a9s Data Service version:

    • a9s MySQL 10.4: MariaDB 10.4 is end-of-life by their vendor since June 2024

    The creation of new a9s Data Service Instances for this deprecated version is now disabled by default in the a9s Data Service Bundle and we no longer provide regular support for this version. The corresponding documentation has been removed.

    Although we will not intentionally break running Service Instances of this unsupported version, it cannot be guaranteed that they still work as expected after an update to this release.

Removed​

  • docs: all services: Remove outdated information about a9s MySQL within the scope of unsupporting a9s MySQL.

Fixed​

  • a9s-pg: a9s PostgreSQL 15: Fix race condition in the a9s PostgreSQL Info Webservice Switchover, where during the switchover operation, the checkpoint LSN location would change while a9s PostgreSQL Info Webservice is executing the election to promote a new node to primary. This could cause an extended downtime during the deployment update and could even lead, in some situations, to an unhealthy cluster after a failover.
  • a9s-pg: a9s PostgreSQL: Fix race condition between the a9s PostgreSQL Info Webservice Failover Monitor and repmgrd, where during a repmgrd failover that could make repmgrd lose track of the correct view cluster sometimes led to a broken cluster with a standby that is not able to follow the new primary.
  • a9s PostgreSQL: a9s PostgreSQL 17: Fix the issue where, during the failover, the checkpoint LSN location would change while repmgrd is executing the election to promote a new node to primary, this could cause an extended downtime during the deployment update, and could even lead, in some situations, to an unhealthy cluster after a failover. This is fixed by enabling repmgr's standby_disconnect_on_failover configuration property.
  • a9s PostgreSQL: a9s Logstash: Fix connection initialization logic causing the Logstash process in a9s PostgreSQL Service Instances to fail during upgrades from single Service Instances to cluster Service Instances. This issue prevented instances from being marked healthy from the director, and occurred during the time in which the replica nodes synchronize with the primary node in the cluster.
  • a9s PostgreSQL: Fix race condition between the a9s PostgreSQL Info Webservice Failover Monitor and repmgrd, where a repmgrd failover could cause repmgrd to lose track of the correct view of the cluster, potentially led to a broken cluster with a standby that is not able to follow the new primary.
  • a9s PostgreSQL: Fix race condition in the a9s PostgreSQL Info Webservice Switchover, where during the switchover operation, the checkpoint LSN location would change while a9s PostgreSQL Info Webservice is executing the election to promote a new node to primary. This could cause an extended downtime during the deployment update and could even lead, in some situations, to an unhealthy cluster after a failover.
  • docs: Application Developer: all services: Fix recurring typos across all the a9s Data Services' index pages.

Security​

  • all services: a9s Backup Agent: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
    • CVE-2025-27610
    • CVE-2025-27788
  • all services: a9s BOSH Deployer: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
    • CVE-2025-27788
  • all services: a9s CF Service Guard: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
    • CVE-2025-27610
  • all services: a9s Deployment Updater:
    • CVE-2025-27788
  • all services: a9s Service Broker: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
  • all services: a9s Smoke-Tests: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • all services: a9s SSO Proxy: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s Backup Services: a9s Backup Monit: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s Backup Services: a9s Backup Manager: Fix CVEs:
    • CVE-2025-27788
    • CVE-2025-27610
  • a9s Billing: Fix CVEs:
    • CVE-2024-56171
    • CVE-2025-24928
  • a9s KeyValue: a9s KeyValue SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s LogMe2: a9s LogMe2 SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s MariaDB: a9s MariaDB SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s Messaging: a9s Messaging SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s MongoDB: a9s MongoDB SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s PostgreSQL: a9s PostgreSQL SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27111
    • CVE-2025-25184
  • a9s Prometheus: a9s Prometheus SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s Redis: a9s Redis SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788
  • a9s Search: a9s Search SPI: Fix CVEs:
    • CVE-2025-27610
    • CVE-2025-27788