Skip to main content
Tungsten Dashboard

Tungsten Dashboard 8.0.4

Build: 67
Release Date: 10 Mar 2026
Release 8.0.4 contains a number of bug fixes and improvements to usability.

Improvements, new features and functionality (7)

Installation and Deployment (3)

    • Kubernetes installation script now allows user to enter certificate key and file to automatically create Kubernetes secret into dashboard namespace.
    • Kubernetes installation no longer requires user to manually enter tls secret and domain details in to the helm values file. They will be automatically filled by the install script.
    Issue: TD2-272
  • Kubernetes installation now prompts user to add Tungsten clusters to the Dashboard. By providing namespace details and selecting the correct Kubernetes service a cluster can be added to the dashboard with the install script if the Tungsten cluster was installed inside the same Kubernetes cluster as the dashboard
    Issue: TD2-271
  • The install script now lets you choose which namespace the dashboard is deployed into, defaulting to tungsten-dashboard, and detects conflicts when a dashboard already exists in a different namespace
    Issue: TD2-266

General usability and Performance (4)

    • Updated cluster status icons for topology warnings.
    • The "Fetch Certs" action now displays a pending message while the operation is in progress.
    • SSL status icon now shows a more specific tooltip indicating whether TCP, API, or both connections are unsecured.
    Issue: TD2-287
    • Added a compact layout mode that reduces cluster row height and spacing for a denser overview; toggle between compact and relaxed layout via the submenu toolbar.
    • Replaced the fixed simple/advanced view toggle with a column selector dropdown in the table header, allowing users to show or hide individual columns (replicator state, latencies, sequence numbers, pipeline, etc.).
    • Column visibility and layout preferences are persisted in local storage across sessions.
    Issue: TD2-284
  • Added host:port syntax support and smart port inference to getcert.pl
    Issue: TD2-279
  • Diagnostic tool now collects dynamic/clusters.edn content in Docker dashboard diagnostics.
    Issue: TD2-277

Bug Fixes (10)

Installation and Deployment (6)

    • Fixed Kubernetes installer to correctly report deployment failures instead of showing misleading "Installation completed!" messages.
    • Added automatic StorageClass detection and configuration to prevent pods from getting stuck in Pending state on clusters without a default StorageClass.
    Issue: TD2-288
  • Feature for fetching certificates automatically now works for hybrid SSL setups. Improved connections handling for clusters with hybrid SSL.
    Issue: TD2-282
  • Kubernetes install did not store repository and registry information correctly into helm values.yaml file. New system stores registry and repository into separate fields in the file.
    Issue: TD2-273
  • Kubernetes installation's "wait for available" condition has had its timeout increased from 30 to 60 seconds to reduce timeout errors at the last step of Kubernetes installations.
    Issue: TD2-269
  • Kubernetes & docker install no longer prints invalid https url at the end of the installation process when https was not enabled
    Issue: TD2-268
  • Kubernetes installation no longer modifies values.yaml file after user has been prompted to validate it
    Issue: TD2-267

General usability and Performance (4)

  • REST URL construction now validates that a target host is present before making a call, providing a clear error message instead of a cryptic HTTP client failure.
    Issue: TD2-283
  • Improved error handling around cluster actions. System now shows more clear errors if host data is missing or corrupted.
    Issue: TD2-281
  • Fixed a bug where a failed REST status poll could erase service connection options, causing subsequent commands to produce malformed URLs.
    Issue: TD2-280
  • Fixed a bug where a failed initial connection to a node with an unresolvable hostname could corrupt cluster state, causing subsequent commands to fail with a missing host target
    Issue: TD2-276