Dash Enterprise 6 features several major improvements. This page can help you understand the key differences between the Dash Enterprise 5 and 6 series.
Designed for multi-node clusters: Dash Enterprise 6 can run in Kubernetes clusters consisting of at least 2 nodes. For full cluster requirements, see Dash Enterprise 6 Installation.
Multi-tenancy: Dash Enterprise 6 doesn’t require a dedicated Kubernetes cluster. You can run other applications, as well as other instances of Dash Enterprise 6, in the cluster. All system components are scoped to safely share a cluster with other tenants.
Simplified install and upgrade: Installing and upgrading Dash Enterprise 6 is done via Helm charts. Helm was chosen for its wide use as a proven package manager for Kubernetes-based software. Compared to Dash Enterprise 5, installing and upgrading Dash Enterprise 6 involves less time and fewer commands. In addition, the image bundle for Dash Enterprise 6 is significantly smaller.
Backup and restore: Dash Enterprise 6 comes with a new in-product backup and restore solution. Once your backup storage is set up, all backup and restore operations, including managing schedules, can be done directly in Dash Enterprise. Learn more at Backing Up and Restoring Dash Enterprise.
Workload identity for apps: With Dash Enterprise 6, apps can be configured to assume the role of Kubernetes service accounts in the cluster, provided an administrator grants permission. This lets app developers fetch data from private buckets, for example, without ever being given sensitive bucket credentials. Learn more at Workload Identity for Apps.
GitHub integration: You can optionally integrate your GitHub organization with Dash Enterprise 6, allowing app source code to live in existing or new GitHub repositories that use your favorite patterns and workflows.
App image storage: Images for apps deployed to Dash Enterprise 6 can optionally be stored in a private container registry that you provide.
Security: Several system components have been reviewed to ensure they operate with least-privilege permissions.