ADS Control releases

Added support for managing ACL in Kafka

Moved the distribution to Ansible 2.16

Improved cluster performance

The page display logic was synchronized for additional components (tabs Cruise Control, Kafka Connect, and Schema Registry). Tabs and services on the main page are now unavailable if the corresponding components and/or services are missing in the cluster

Fixed an issue that occurred when reading messages — by default, only messages from one segment were displayed

Fixed an issue that occurred when changing the number of topic partitions — after setting a value lower than the current one, it was impossible to continue editing

Fixed an issue that occurred when resending a message with the same value — an empty message was sent

Minimum ADCM version — 2.9.0

Removed the ability to compare schemas when only one version of the schema is available

Fixed sorting for large numerical values in tables

Fixed an issue that occurred when sending a message in a format other than JSON

Fixed issues that occurred when reading a message if the cluster does not have the Schema-Registry service

Fixed an issue that occurred when applying a Cruise Control proposal — rebalance was not performed due to the default dry-run mode being enabled for requests

Fixed an issue that occurred when sending a message to a specified partition

Fixed a crash of FileStreamSinkConnector that occurred when publishing messages to a topic

Release 2.6.1 was skipped due to critical vulnerabilities

Added support for Astra Linux 1.7 "Voronezh"

Added support for AltLinux 10 SP

By default, Java 21 is pre-installed from the arenadata repository for installing the ADS Control service

A utility has been implemented for explicitly selecting Java for the service

Docker is no longer required to install the ADS Control service

Added the ability to change the number of partitions on the Clusters → <cluster name> → Topics → Partitions tab

Added the ability to write messages in the Avro format

Improved display of message keys and large messages when reading

Added the ability to use a schema template when writing a message

Messages in the Avro format are now converted to a readable format when integrating with Schema-Registry

Fixed incorrect response status code when updating topics in some cases

This version adds the ability to automatically install Java from an Arenadata repository when installing a cluster. However, Arenadata is not an official JDK provider, and this feature is provided to ensure a fully automatic installation on systems that do not have the necessary dependencies. In production environments, we recommend using a JDK from official providers

Minimum ADCM version — 2.8.0

In this version, the Cruise Control tab requires Kerberos authentication and SSL to be enabled on the ADS cluster. This issue will be fixed in the next version

Added the ability to view a list of schemas associated with a topic

Added schemа verification during creation of schemas

Implemented support for SASL_PLAINTEXT authentication in ADS

Fixed incorrect usage of the keystore and truststore variables

Fixed: a consumer group was not deleted after inactivityTimeout expired

Fixed an issue when creating a consumer group with offsetType=latest

Fixed creating schemas with the same ID

Fixed incorrect operation of filters on the connector plugin selection page

Fixed an issue with hiding the error stack trace panel after a successful restart of a task

Fixed an issue that occurred when setting predicates.hasDateValue.type and transforms.dateToString.type parameters for newly created Kafka connectors

Minimum ADCM version — 2.5.0

Implemented the AuthZ plugin (for Ranger)

Implemented the Schema Registry page for viewing and managing schemas

Support for synchronizing users with an LDAP directory

Support for setting up Tiered Storage when creating a topic on the Topics page

After the ADS Control SSL interface, all Kafka topic enable metadata (size, number of messages, etc.) was displayed, but the messages were not loaded

Incorrect behavior after deleting the last topic or shifting the consumer group partition

Page size settings combobox was not available in the consumer group offset editing form

Filtering messages by Start offset did not work correctly

Password field was not displayed when creating the Debezium MSSQL/Postgres connector

Request for consumer groups for a non-existent topic did not fail with a 404 error

Implemented the Consumer groups overview page for reviewing and managing consumer groups

Implemented support for RedOS

Added the Advanced docker settings group of configuration parameters to control the installation of the Docker package before installing the ADS Control cluster

Fixed issue with updating the broker state when stopping/starting the Kafka service

Fixed incorrect display of values ​​in the input data for editing topic parameters after changing the configuration via the CLI

Fixed issue with updating connector parameters in the UI after an external change

Implemented the General cluster overview page

Implemented the Brokers overview page

Added new cluster actions: Manage Kerberos and Manage SSL

Implemented the ability to work with secure (SSL, Kerberos) Kafka clusters

After running cluster upgrades, re-enable SSL on the cluster via the Manage SSL action if it was enabled before the upgrade

Implemented support for Astra Linux

Revised user management to use secretmap entries in the ADCM interface

Changed product name to ADS Control, made appropriate changes to ADS Control UI

Changed container version to 2.1.1

Updated user agreement

Fixed incorrect display of the cluster status in the ADCM interface after installation