Homepage

Cloudera on Cloud: June 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.50-b68 and MLX-CRUD-APP 1.50.0-b139 introduces the following changes:

New Features / Improvements

Cloudera AI Platform

  • Added support for Azure AMD Easv5 instances. (DSE-38566)

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

ML Runtimes 2025.06.1 introduces the following improvements:

  • CVE fixes - This maintenance release includes numerous improvements related to Common Vulnerability and Exposures (CVE).
  • The R major version has been upgraded to 4.5
  • Python 3.13 minor version has been added
  • Additional OS packages added to the R runtime to allow the installation of R libraries
  • Existing Python maintenance versions have been upgraded to:
    • Python 3.9.22 (from 3.9.21)
    • Python 3.10.17 (from 3.10.16)
    • Python 3.11.12 (from 3.11.11)
    • Python 3.12.10 (from 3.12.8)

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

Cloudera Data Catalog

Cloudera Data Catalog 3.1.1 introduces the following new changes:

  • Profilers in Compute Cluster enabled environments now support profiling text based files. Custom delimiters are supported for Hive tables where the Hive Metastore contains them. Cloudera Data Catalog now supports LazySimpleSerDe for Hive tables. For more information, see the Apache Hive DeveloperGuide.
  • This release contains fixes and updates for the changes in the 3.1.0 release. For more information, see the list of fixed and known issues.

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

Cloudera Data Engineering

Cloudera Data Engineering 1.23.1-H3 contains a fix for Apache Parquet CVE-2025-30065. For more information, see the Cloudera Data Engineering Release Notes.

Cloudera Data Engineering 1.24.1 introduces the following changes:

Suspending and resuming Cloudera Data Engineering Services - Technical preview
The suspend and resume feature enables you to temporarily pause your entire Cloudera Data Engineering Service during idle periods. Suspending Services when they are not needed offers significant cost savings, primarily on compute resources, while ensuring that the Services remain available when required. During suspension, all Service and Virtual Cluster configurations and Jobs are preserved. By default, the entitlement for the suspend and resume feature is disabled. For more information, see Suspending and resuming Cloudera Data Engineering Services.

Security hardened image
Starting with Cloudera Data Engineering version 1.24.1, a new security-hardened image is introduced to enhance security and increase resilience against Common Vulnerabilities and Exposures (CVEs). In Cloudera Data Engineering version 1.24.1, you have the option to choose between adopting the new security hardened image or continuing to use the existing image from previous versions (Redhat UBI), based on your system needs and business requirements.

The runtime component versions are upgraded in the security hardened image; for compatibility, see Compatibility for Cloudera Data Engineering and Runtime components. For information on the upgrade behavior of the security hardened image, see Cloudera Data Engineering upgrade version compatibility.

Git integration support available for GA
The Git integration support feature, previously available as a technical preview, has now reached General Availability (GA). For more information, see Creating a Git repository in Cloudera Data Engineering.

Autoscaling range setting method enhanced on the Cloudera Data Engineering UI
While creating a new Cloudera Data Engineering Service on the Cloudera Data Engineering UI (Administration > Enable a Service), you have the option to set the autoscaling range for the Core and All-Purpose Tiers. In the Capacity & Costs section, you can configure the autoscaling range for On-demand instances and if you select an AWS environment, for Spot instances as well. For more information, see Cloudera Data Engineering tier types.

Runtime component version exposure on the Cloudera Data Engineering UI
On the Cloudera Data Engineering UI, you can view the Apache Airflow runtime components and Spark runtime components on the creation and details pages of a Service, Virtual Cluster, job, or session.

Runtime component version behavior after upgrading
To maintain backwards compatibility, the in-place upgrade does not modify the image type, and after the upgrade to Cloudera Data Engineering version 1.24.1, the old RedHat (deprecated) images continue to be used. To use the new, security hardened image, after the upgrade, you must create new Virtual Clusters and select the new image. For more information on the supported runtime components, see Compatibility for Cloudera Data Engineering and Runtime components.

Cloudera Data Engineering private network for Elastic Kubernetes Service and Azure Kubernetes Service available for GA
Enabling a fully private network for a Cloudera Data Engineering service for Azure and Enabling a semi-private network for a Cloudera Data Engineering service with AWS are available for GA. For more information, see:

Kubernetes version upgrade to 1.31
The Kubernetes version that Cloudera Data Engineering uses is upgraded to Kubernetes 1.31. For more information, see Compatibility for Cloudera Data Engineering and Runtime components.

Apache Airflow version upgrade to 2.10.4
The Airflow version that Cloudera Data Engineering uses is upgraded to Airflow 2.10.4. For more information, see:

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

Cloudera Data Hub

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

Selecting Architecture for Cloudera Data Hub on AWS
When creating a Cloudera Data Hub cluster on AWS, you can select from the following architecture types:

  • X86_64
  • ARM64 When you choose the architecture type, the compatible images and cluster templates will be available for the Cloudera Data Hub cluster.

Cloudera Data Engineering support on ARM - GA
With the Cloudera Runtime 7.3.1.300 Service Pack 1 (SP1) Cumulative Hotfix 1 (CHF1) release, deploying Cloudera Data Engineering Data Hub clusters using ARM processors are now generally available.

For more information about how to create Cloudera Data Engineering Data Hub clusters on ARM processors, see the Creating a cluster from a definition on AWS documentation.

The following limitations are applied when using the ARM-based architecture:

  • You can create ARM-based Cloudera Data Engineering Data Hub clusters only in Cloudera environments on AWS.
  • Ensure that the EC2 instances with ARM processors are supported in your region. For more information, see the AWS Graviton Processors and Amazon EC2 instance types by Region documentation.
  • From the available Cloudera Data Hub templates, only the Data Engineering templates are supported on the ARM-based architecture.
  • Clusters with mixed architectures are not supported. All cluster nodes should have the same architecture, either X86_64 or ARM64.

Cloudera Data Warehouse

Cloudera Data Warehouse 1.10.2-b158 does not introduce new features, but includes fixes. For more information, see the Cloudera Data Warehouse Release Notes.

Cloudera Management Console

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

Cluster Connectivity Manager v1 - End of Life (EoL) update
As previously communicated in Cloudera Customer Advisory-824, Cluster Connectivity Manager v1 has reached its EoL by April 10, 2025 in favor of Cluster Connectivity Manager v2.

The Cluster Connectivity Manager v1 infrastructure has been shut down on April 10, 2025. All traffic on the Cluster Connectivity Manager v1 channel has been blocked. Starting June 4th, Cloudera has initiated a phased decommissioning of the infrastructure to remove Cluster Connectivity Manager v1 from Cloudera on cloud and on premises.

For more information about the discontinuation of Cluster Connectivity Manager v1, see Cloudera Customer Advisory-824: Cluster Connectivity Manager v1 will be discontinued on April 10, 2025.