-
Notifications
You must be signed in to change notification settings - Fork 46
doc: write tcm release notes #5584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| .. _tcm_releases_1_6: | ||
|
|
||
| Tarantool Cluster Manager 1.6 | ||
| ============================= | ||
|
|
||
| Release date: February 6, 2026 | ||
|
|
||
| Latest release in series: 1.6.0 | ||
|
|
||
| This release introduces support for Tarantool DataBase (TDB) workers in the cluster dashboard with integrated health monitoring, | ||
| adds TLS configuration guides for secure connections, improves audit log configuration and validation, | ||
| and introduces a feature flag for managing the **Tuples** tab. It also includes important fixes for LDAP authentication, | ||
| TLS configuration parsing, and a memory leak in SSL cluster connections. | ||
|
|
||
| .. _tcm_releases_1_6_workers_tdb: | ||
|
|
||
| TDB workers monitoring in cluster dashboard | ||
| -------------------------------------------- | ||
|
|
||
| |tcm| adds support for TDB workers in the cluster **Stateboard** tab with integrated health monitoring and visibility. | ||
|
|
||
| TDB workers are supported starting from TDB 3.1.0. | ||
| Workers are automatically discovered from etcd and continuously monitored via dedicated health check endpoints. | ||
| Their metrics are proxied through TCM and exposed individually, allowing detailed operational insight. | ||
|
|
||
| The interface displays workers directly in the stateboard with clear status indicators and a details panel. | ||
| Each worker can be in one of four statuses: healthy, degraded, unhealthy, or no connection, helping administrators quickly detect and diagnose issues. | ||
|
|
||
| To learn more, see `TDB documentation <https://www.tarantool.io/ru/tarantooldb/doc/latest/examples/tdb_worker/tdb_worker_example/>`__. | ||
|
|
||
| .. _tcm_releases_1_6_audit_log: | ||
|
|
||
| Audit log configuration improvements | ||
| ------------------------------------ | ||
|
|
||
| The audit log configuration is now safer and more predictable. | ||
|
|
||
| Protocol values are validated during startup. If an invalid protocol is specified, the system automatically falls back to default settings and emits a warning. | ||
| 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. | ||
| These settings will be applied automatically if the audit log has not been configured yet. | ||
|
|
||
| .. _tcm_releases_1_6_explorer: | ||
|
|
||
| Explorer enhancements | ||
| --------------------- | ||
|
|
||
| A feature flag has been introduced to control the visibility of the **Tuples** tab in the Explorer interface. | ||
|
|
||
| The tab is displayed only when the corresponding feature flag is enabled and the CRUD module is available. | ||
| The flag can be configured either in the TCM configuration file or via command-line arguments at startup. | ||
|
|
||
| To enable the **Tuples** tab in the TCM configuration file: | ||
|
|
||
| .. code-block:: yaml | ||
|
|
||
| # tcm.yaml | ||
| feature: | ||
| tuples: True | ||
|
|
||
| .. _tcm_releases_1_6_fixes: | ||
|
|
||
| Stability and reliability fixes | ||
| ------------------------------- | ||
|
|
||
| This release also includes several fixes that improve system stability and security. | ||
|
|
||
| LDAP authentication behavior has been adjusted, including logout handling, anonymous binding to Active Directory, and the preservation of authorization method settings after a restart. | ||
| TLS configuration parsing has been fixed to ensure cipher suites and curve preferences are correctly recognized in both configuration files and command-line arguments. | ||
| Missing schema attributes for cluster configuration have been added, and configuration validation feedback in the editor has been improved. | ||
|
|
||
| Additionally, a memory leak that could occur when SSL-enabled cluster connections became unavailable has been resolved, resulting in more stable cluster operation. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| .. _tcm_releases_1_7: | ||
|
|
||
| Tarantool Cluster Manager 1.7 | ||
| ============================= | ||
|
|
||
maryiaLichko marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| Release date: February 11, 2026 | ||
|
|
||
| Latest release in series: 1.7.1 | ||
|
|
||
| This release introduces control over automatic default cluster creation, | ||
| improves LDAP authentication handling, and enhances user management capabilities in the UI. | ||
|
|
||
| .. _tcm_releases_1_7_cluster_management: | ||
|
|
||
| Default cluster management | ||
| -------------------------- | ||
|
|
||
| You can now control automatic creation of the default cluster using one of the following options: | ||
|
|
||
| - ``TCM_DEFAULT_CLUSTER`` environment variable | ||
| - ``default-cluster`` configuration parameter | ||
| - ``--default-cluster`` command-line flag | ||
|
|
||
| This allows administrators to explicitly enable or disable default cluster auto-creation depending on deployment requirements. | ||
|
|
||
| .. _tcm_releases_1_7_improve_ldap: | ||
|
|
||
| LDAP authentication improvements | ||
| -------------------------------- | ||
|
|
||
| Error handling has been improved for LDAP authentication when the **Automatically add non-existent users** option is disabled. | ||
|
|
||
| It is also now possible to create a user via the UI with LDAP authentication enabled, simplifying user management in LDAP-based environments. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.