Homepage

Cloudera on Cloud: May 2025 Release Summary

The Release Summary of Cloudera Public Cloud summarizes major features introduced in Management Console, Data Hub, and data services.

Cloudera AI

Cloudera AI 2.0.50-b68 introduces the following changes:

New Features / Improvements

Cloudera AI Workbench

  • AI Studios (Technical Preview): Cloudera AI Studios is a comprehensive suite of low-code tools designed to simplify the development, customization, and deployment of generative AI solutions within enterprises. This suite empowers organizations to operationalize AI workflows quickly and efficiently by leveraging real-time enterprise data. For more information, see Managing AI Studios.
  • Added APIs within the workbench to list Cloudera AI Inference service applications and their associated model endpoints.

Cloudera AI Platform

  • Added Azure UDR support for Cloudera AI Inference service.
  • Added Azure NTP support.
  • Added API support to retry the creation of Cloudera AI Inference service application upon failure.

Cloudera AI Registry

  • Added a new set of models in the Model Hub, including Llama3.3, DeepSeek-R1-Distill-Llama, Starcorder2, Llama-Nemotron-Nano, NeMo-Retriever-Parse, Llama 3.2 Embedding, and Llama 3.2 Encoder models. To access these models, you must upgrade your Cloudera AI Registries.
  • Added support for nim-cli in the AI Registry to import the latest offerings from NVIDIA.
  • Enhanced troubleshooting by surfacing underlying issues encountered during AI Registry installation in the Event logs.
  • Provided the ability to upgrade the AI Registry directly through the UI, eliminating the reliance on the CLI.
  • Implemented automatic redirection to the model import status page whenever a new model import is triggered.

Cloudera AI Inference service

  • Users must upgrade their Cloudera AI Inference service applications to serve the latest optimized models from NVIDIA, including Llama3.3, DeepSeek-R1-Distill-Llama, Starcorder2, Llama-Nemotron-Nano, NeMo-Retriever-Parse, Llama 3.2 Embedding, and Llama 3.2 Encoder models.
  • Optimization profile details for deployed model endpoints are now surfaced in the UI for improved visibility.
  • A user-friendly warning message will now be displayed when replicas of a deployed model scale down.
  • Added an option in the UI to retry the creation of Cloudera AI Inference service applications.
  • Users will be automatically redirected to the model endpoint page upon triggering the deployment of a new endpoint.
  • Enhanced the UI with a variety of user-friendly tooltips for better usability.
  • The metrics page for model endpoints will now refresh automatically every 15 seconds for real-time updates.
  • GPU count is now auto-selected for NIM profiles when deploying a model endpoint.
  • Ensured that dangling pods of deleted endpoints are immediately terminated, preventing them from being left for garbage collection cleanup.

For more information about the Known issues, Fixed issues and Behavioral changes, see the Cloudera AI Release Notes.

Cloudera Data Flow

Release 2.10.0-h1-b1 of Cloudera Data Flow introduces fixes to the Cloudera Data Flow UI and platform, such as tooltip persistence, incorrect property displays, and navigation failures, enhancing overall functionality and user experience.

Release 2.10.0-h2-b1 of Cloudera Data Flow fixes an issue where a flow draft referencing multiple shared parameter groups, or multiple flow drafts referencing the same parameter group caused upgrades to fail.

For more information about the Known issues, Fixed issues and Behavioral changes, see the Cloudera Data Flow Release Notes.

Cloudera Data Hub

The latest version of Cloudera Data Hub introduces the following changes:

Secret rotation - GA
To add extra measures of security, you can rotate secrets, like database passwords or FreeIPA admin password using CLI commands. These secrets are managed and created by the Cloudera Control Plane. By using the following commands the secrets can be rotated to achieve more secure deployments. For more information, see Rotating Cloudera Data Hub secrets documentation.

Restarting instances from Cloudera Management Console
You can now restart Cloudera Data Hub instances using the Cloudera Management Console. For more information, see the Restarting Cloudera Data Hub instances documentation.

Cloudera Management Console

The latest version of Cloudera Management Console introduces the following changes:

Secret rotation - GA
To add extra measures of security, you can rotate secrets, like database passwords or FreeIPA admin password using CLI commands. These secrets are managed and created by the Cloudera Control Plane. By using the following commands the secrets can be rotated to achieve more secure deployments.

For more information, see the following documentations:

Restarting instances from Cloudera Management Console
You can now restart Data Lake instances using the Cloudera Management Console. For more information, see the Restarting Data Lake instances documentation.

Updated Minimal policy for AWS
The Minimal policy that is required for accessing AWS resources for Cloudera on cloud has been updated to limit the permissions for deleting resources. The updated Minimal policy can be found here or in the Reduced access policy definition documentation.

Cloudera Operational Database

The Cloudera Operational Database 1.51 version supports multiple enhancements and the removal of an entitlement.

Enhancements to the CacheAwareLoadBalancer feature
You can set the hbase.master.scp.retain.assignments property to true in Cloudera Manager when using the Cloud Storage with Caching storage type for your Cloudera Operational Database. This configuration enhances the CacheAwareLoadBalancer and persistent bucket cache features. This enhancement takes effect automatically for the Cloudera Operational Database created with version 1.51.0 or later.

Enhancements to the Cloudera Operational Database UI
In the Cloudera Operational Database UI, when you click on a database, the Database Manager page displays only the key parameters. The remaining parameters are collapsed under a header. Click the header to view the additional parameters.

The COD_USE_I3_INSTANCE_TYPE entitlement removal
The Cloudera Operational Database has removed the COD_USE_I3_INSTANCE_TYPE entitlement because it is no longer needed. You can use the --custom-instance-types option in the create-database command that allows you to choose the I3 instance types (non-default) for the Cloudera Operational Database.

For more information, see CDP CLI documentation.

The Cloudera Operational Database 1.52 version supports enhancements to the Cloudera Operational Database UI.

Enhancements to the Cloudera Operational Database UI
Within the Cloudera Operational Database user interface, a Nodes tab is integrated into the Databases > Database Manager. This tab lists all the supported host group nodes that are actively executing within the Cloudera Operational Database cluster. For each host group node, detailed information is provided, including the Interface ID, Fully Qualified Domain Name (FQDN), Instance Type, Subnet ID, Availability Zone, Public IP address, and Private IP address.

For more details, see Nodes.

For more information about the Fixed issues, Known issue, and Behavioral changes, see the Cloudera Operational Database Release Notes.

Cloudera Replication Manager

This release of the Replication Manager service introduces the following new features.

Retry the creation process for failed HBase replication policies
You can use the Actions > Retry Failed Create option for HBase replication policies to retry the HBase replication policy creation process. This option appears for failed HBase replication policies that show the Create failed status. You can view the replication policy status on the Replication Manager > Replication Policies page.

For more information, see Monitor HBase replication policy job details.

For more information about the Fixed issues, Known issue, and Behavioral changes, see the Cloudera Replication Manager Release Notes.