Domino 6.0.1 (December 2024)

Improvements

When registering a Data Plane with Dataset support, you can now define more granular configurations listed in the Enable Datasets in Nexus section.

If you have Domino Governance enabled, Jira Integration for Tasks now functions as expected. You can find Tasks on the Project Overview page.

Users can see raw files whose size is ⇐ 5 MB (com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes) when they click on the "View Raw File" button, even if their Artifacts file viewer doesn’t have CORS enabled in the blob storage provider.

Users with special characters like @ in their usernames can now successfully run Flows.

External endpoints can now be created for AWS account IDs that start with a zero.

External Endpoints in the Starting or Failed state will now expose their Instance Logs through Domino.

Updating the registered model/version of an external endpoint will reload the starting/running Sagemaker endpoint.

Users can now create an external endpoint from a global model even if they are not a collaborator on the model’s project.

External Endpoints in the Failed state will now correctly rebuild and redeploy when updated.

Running apps within VS Code workspaces successfully render through VS Code port proxy.

Flows is only supported in Domino Cloud, AWS, and Azure. A future update will add support for Google Cloud and on-premises installs.

Some Flyte features are not yet available in Flows, such as dynamic workflows, eager workflows, and map_task.

When annotating a Domino Flows sub workflow’s outputs as a Flows Artifact, the artifacts will not be properly exposed in the Artifacts UI for that Flow.

In Azure Blob Store deployments, Projects with many files may fail to sync through the Domino CLI. To work around this issue, do not disable file locking when prompted by Domino.

You cannot view the latest raw file if you click View Latest Raw File. In the navigation pane, go to Files and click a file to view its details.

When uploading a large file to the Azure blob store by syncing a Workspace, you may encounter a Java Out of Memory error from Azure if the file/blob already exists. To work around this issue, use the Domino CLI to upload the file to the Project.

Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry, because the name points to an invalid bucket.

Domino instances that make use of Azure Blob Storage may experience stalled Jobs within Projects with many large files.

If you attach a Git repository to a DFS Project that points to a tagged release, the tag won’t be honored when building a Domino endpoint in that Project. The build log will show an error similar to the following, and the model will be built using the default branch of your Git repository instead of the tagged branch:
```
Jul 05 2023 14:36:27 -0500 #10 6.481 WARN [d.r.d.GitRepoUpdater] could not parse ref: v1.3.0 checking out default branch correlationId="iA2qWrYSLQ" thread="main"
```
To work around this issue, use the branch name when building Domino endpoints instead of the release tag.

If an admin resets a user’s password, it invalidates all the user’s authentication tokens, including tokens used for long-running tasks like Jobs, Workspaces, or Apps. The user must create a new password, log back into Domino, and restart all executions. This also applies to CLI authentication; the user must re-login to their Domino CLI.

The following versions have been validated with Domino 6.0.1. Other versions might be compatible but are not guaranteed.

GKE users that provisioned their infrastructure with Domino’s terraform-gcp-gke module must apply the changes introduced for 5.7.0 as of terraform-gcp-gke v2.5.0 when upgrading to ensure firewall rules work properly.

GKE Kubernetes version compatibility is updated to 1.30 / 1.29.
VPN support from within executions was updated to be disabled by default. Support can be enabled by setting the global config value com.cerebro.domino.computegrid.executions.allowVpn = true.

EKS users are recommended to update the AWS VPC CNI settings to enable ANNOTATE_POD_IP to prevent execution timeout errors when an image pull takes longer than 10 minutes. To bypass the validation check during an upgrade, pass --warn-only as a command line option to the installer.

For customers using the platform sizing guide, it is now recommended to use 16 core / 64 GB (or higher) platform node instances.

EKS users who provisioned their infrastructure with Domino’s terraform-aws-eks module must validate whether they want the new costs blob storage to be provisioned by default.

The new Data Plane version has advanced to a major release (now 4.1.1-3). As a result, the upgrade button will not function due to the version gap. To complete the upgrade successfully, a manual process is required. For details, refer to the upgrade the Data Plane section.