Homepage

Cloudera on Cloud: August 2025 Release Summary

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

Cloudera AI

Cloudera AI 2.0.52-b34 introduces the following changes:

ML Runtimes

  • Released new Spark Runtime Addons versions - 2.4.8, 3.2.3, 3.3.0, and 3.5.1.
  • Spark 3.5.1 in Cloudera AI is now certified to work with the Data Lake 7.3.1 version.
  • New HadoopCLI Runtime Addon versions 7.2.18 and 7.3.1 are now available. Versions 7.2.16 and 7.2.17 have been removed.

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

ML Runtimes 2025.09.1 introduces the following improvements:

  • CVE fixes: This major release includes numerous improvements related to Common Vulnerability and Exposures (CVE).

  • Freshline Runtimes: Freshline Runtimes are a new variant of ML Runtimes designed for users who prioritize the latest software with fewer security vulnerabilities:

    Unlike our other runtimes, which are built on Ubuntu LTS (Long-Term Support) releases, Freshline Runtimes use the newest interim (non-LTS) Ubuntu releases.

    • Benefit: These runtimes offer a significantly lower number of security vulnerabilities since they are based on a more recent base image.
    • Drawback: The support window for non-LTS Ubuntu images is much shorter. To address this, Cloudera will upgrade the base Ubuntu image every six months, which may introduce breaking changes. Additionally, we may introduce other breaking changes to these images in any Runtime release, regardless of a base image upgrade.

    Note
    Cloudera will only provide support and fixes for the most recent Freshline Runtime releases. We cannot guarantee multi-year support for older versions of Freshline Runtimes, so you must stay current to receive the latest updates.

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

Cloudera Data Hub

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

Selecting preferred zones for multi-AZ Cloudera Data Hub clusters on Azure
When scaling a multi-AZ Cloudera Data Hub cluster, the new nodes are automatically distributed across all available availability zones. However, if you prefer to manually control the distribution of nodes during the Cloudera Data Hub scaling, you can use the --preferred-zones field. For more information, see the Creating a multi-AZ Cloudera Data Hub cluster on Azure documentation.

Cloudera Data Warehouse

Cloudera Data Warehouse 1.10.3-b8 introduces the following changes:

What’s new in Cloudera Data Warehouse on Azure environments

Azure AKS 1.32 upgrade
Cloudera supports the Azure Kubernetes Service (AKS) version 1.32. In 1.10.3-b5 (released August 05, 2025), when you activate an Environment, Cloudera Data Warehouse automatically provisions AKS 1.32. To upgrade to AKS 1.32 from an earlier version of Cloudera Data Warehouse, you must backup and restore Cloudera Data Warehouse.

Note
Using the Azure CLI or Azure portal to upgrade the AKS cluster is not supported. Doing so can cause the cluster to become unusable and can cause downtime. For more information about upgrading, see Upgrading an Azure Kubernetes Service (AKS) cluster.

What’s new in Cloudera Data Warehouse on AWS environments

AWS EKS 1.32 upgrade
Cloudera supports the AWS Elastic Kubernetes Service (EKS) version 1.32. In 1.10.3-b5 (released August 05, 2025), when you activate an Environment, Cloudera Data Warehouse automatically provisions EKS 1.32. To upgrade to EKS 1.32 from an earlier version of Cloudera Data Warehouse, you must backup and restore Cloudera Data Warehouse.

Note
Using the AWS tools to upgrade the EKS cluster is not supported. Doing so can cause the cluster to become unusable and can cause downtime. For more information about upgrading, see Upgrading an Amazon Kubernetes Service (EKS) cluster.

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

Cloudera Operational Database

Cloudera Operational Database 1.53 introduces the following changes:

Vertical Scaling using the Cloudera Operational Database UI
The Cloudera Operational Database user interface facilitates vertical scaling based on the supported instance types for each node group separately. A Vertical Scaling button has been incorporated into the Nodes tab within the Database Manager page. To initiate vertical scaling, an available instance type provided by a node group can be utilized. The quantity of instance types assigned to each node group is contingent upon the database’s scale type, such as Micro, Light, or Heavy Duty. To ascertain the supported instance types for a given combination of cloud platform, scale type, and storage type, the list-supported-instance-types CLI command can be employed. For more information, see list-supported-instance-types.

Enhancements to the drop database command
A new option --force is added to the CLI command, drop-database. You can use this option to forcibly drop the database. The following is an example of the command using the --force option.

cdp opdb drop-database --environment-name [***ENVIRONMENT NAME ***] --database-name [***DATABASE NAME***] --force

For more information, see drop-database.

Snapshot creation using the Cloudera Operational Database UI
You can create a snapshot of an HBase table using the Cloudera Operational Database user interface. Database table snapshots serve various purposes, including backup and recovery, reporting or analytical functions, and the preservation of regulatory or audit data. These snapshots can subsequently be restored from their designated location to an available target database. To know more about the snapshot creation, see Working with snapshots in Cloudera Operational Database.

Enhancements to the update-hbase-configuration CLI command
The behavior of the following parameters in the update-hbase-configuration CLI command is modified:

  • The --configuration-value option is now an optional parameter.
  • Safety valve items can be added or updated using the --set-safety-valve-item-name and --set-safety-valve-item-value parameters.
  • Safety valve items can be removed using the --unset-safety-valve-item-name parameter.
  • Safety valve modifications do not reorder existing items; new items are appended to the end.
  • The command supports XML, property file, and environment variable safety valves. For more information, see update-hbase-configuration.

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

Cloudera Management Console

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

Transitioning from Azure default outbound access
As previously communicated in Cloudera Customer Advisory-866, Microsoft is planning to retire the default outbound access connectivity for virtual machines in Azure on 30 September, 2025. You must transition your Cloudera environment on Azure to use an explicit method for outbound internet connectivity while creating any new virtual machines. This ensures enhanced security, predictability, and reliability for your clusters. For more information, see the Transitioning from Azure default outbound access documentation.