Versions
Director version numbers track DataStream version numbers. The table below lists the Director versions released to date and the Director changes each one carried. Versions that introduced no Director changes are not listed.
| Version | Description |
|---|---|
| v2.1.0 | Serverless Mode — Directors can be deployed to Kubernetes, Docker, Azure Container Instances, and Azure Container Apps in addition to Windows and Linux hosts. Processing Mode — data storage behavior is configurable per Director: in-memory, crash-resistant, or persistent. |
| v2.0.0 | Director 2.0 — new Director core with faster log collection and processing, and higher sustained throughput. Director Proxy — proxy settings moved into the Director configuration, so connectivity is managed in one place. Director TLS — Director-to-Agent communication can be encrypted in transit. |
| v1.10.4 | Fixed an issue where a high number of entries in the Director configuration could cause errors. |
| v1.10.1 | Director configuration delivery is now version-aware, so Directors running earlier versions handle the Vault configurations introduced in v1.10.0 correctly. |
| v1.10.0 | Fixed an issue where notifications in self-managed Director environments prevented the latest available version from being downloaded. |
| v1.9.0 | Orchestrated Director — Director type for auto-scaling environments in which instances are created, scaled, and replaced by the platform rather than managed directly. Cluster IP — cluster traffic can be routed through a single IP address. |
| v1.8.1 | Fixed Director configuration not being published when a Dataset is created or deleted. |
| v1.8.0 | Update Management — version management for Directors and Agents, with a choice between automatic and manually triggered updates. |
| v1.7.0 | Cluster Director — Directors can run in odd-numbered clusters (3, 5, 7) for quorum-based decisions, with cluster-level configuration distribution and failover. Token authentication and network access controls — Director configurations support token management for credential rotation and revocation, and restriction of Director connectivity to authorized endpoints. |
| v1.6.1 | Fixed configuration strings sent from the web interface to the Director being incorrectly formatted, which caused configurations to fail and blocked data flow. |
| v1.5.0 | Self Managed Director — two configuration management modes. Managed mode pushes configuration changes to the Director automatically; self-managed mode requires the configuration to be downloaded and uploaded to the Director manually, with a warning shown while a newer configuration is pending. |