|
| 1 | +.. _tcm_releases_1_6: |
| 2 | + |
| 3 | +Tarantool Cluster Manager 1.6 |
| 4 | +============================= |
| 5 | + |
| 6 | +Release date: February 6, 2026 |
| 7 | + |
| 8 | +Latest release in series: 1.6.0 |
| 9 | + |
| 10 | +This release introduces support for TDB workers in the cluster dashboard with integrated health monitoring, |
| 11 | +adds TLS configuration guides for secure connections, improves audit log configuration and validation, |
| 12 | +and introduces a feature flag for managing the Tuples tab. It also includes important fixes for LDAP authentication, |
| 13 | +TLS configuration parsing, and a memory leak in SSL cluster connections. |
| 14 | + |
| 15 | +.. _tcm_releases_1_6_workers_tdb: |
| 16 | + |
| 17 | +TDB workers monitoring in cluster dashboard |
| 18 | +-------------------------------------------- |
| 19 | + |
| 20 | +|tcm| adds support for TDB workers in the cluster dashboard with integrated health monitoring and visibility. |
| 21 | + |
| 22 | +Workers are automatically discovered from etcd and continuously monitored via dedicated health check endpoints. |
| 23 | +Their metrics are proxied through TCM and exposed individually, allowing detailed operational insight. |
| 24 | + |
| 25 | +The interface displays workers directly in the stateboard with clear status indicators and a details panel. |
| 26 | +Each worker can be in one of four states: healthy, degraded, unhealthy, or no connection, helping administrators quickly detect and diagnose issues. |
| 27 | + |
| 28 | +.. _tcm_releases_1_6_audit_log: |
| 29 | + |
| 30 | +Audit log configuration improvements |
| 31 | +------------------------------------ |
| 32 | + |
| 33 | +The audit log configuration is now safer and more predictable. |
| 34 | + |
| 35 | +Protocol values are validated during startup. If an invalid protocol is specified, the system automatically falls back to default settings and emits a warning. |
| 36 | +Audit log parameters can be set in advance at the system bootstrap stage by specifying them in the ``auditlog`` field of the initial-settings section in the configuration file. |
| 37 | +These settings will be applied automatically if the audit log has not been configured yet. |
| 38 | + |
| 39 | +.. _tcm_releases_1_6_explorer: |
| 40 | + |
| 41 | +Explorer enhancements |
| 42 | +--------------------- |
| 43 | + |
| 44 | +A feature flag has been introduced to control the visibility of the **Tuples** tab in the Explorer interface. |
| 45 | + |
| 46 | +The tab is displayed only when the corresponding feature flag is enabled and the CRUD module is available. |
| 47 | +The flag can be configured either in the application configuration file or via command-line arguments at startup |
| 48 | + |
| 49 | +.. _tcm_releases_1_6_fixes: |
| 50 | + |
| 51 | +Stability and reliability fixes |
| 52 | +------------------------------- |
| 53 | + |
| 54 | +This release also includes several fixes that improve system stability and security. |
| 55 | + |
| 56 | +LDAP authentication behavior has been adjusted, including logout handling, anonymous binding to Active Directory, and the preservation of authorization method settings after a restart. |
| 57 | +TLS configuration parsing has been fixed to ensure cipher suites and curve preferences are correctly recognized in both configuration files and command-line arguments. |
| 58 | +Missing schema attributes for cluster configuration have been added, and configuration validation feedback in the editor has been improved. |
| 59 | + |
| 60 | +Additionally, a memory leak that could occur when SSL-enabled cluster connections became unavailable has been resolved, resulting in more stable cluster operation. |
0 commit comments