Homepage

Cloudera on Cloud: September 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-b60 introduces the following changes:

New Features / Improvements

Cloudera AI Registry

  • You can now update the visibility of models directly from the UI.
  • You can now delete registries in a failed status directly from the UI.
  • Added the ability to use pre-downloaded artifacts when importing external models.
  • The model card for embedding models now includes MaxTokens, Parameters, and Dimensions.
  • Added support for upgrading Azure registries with UDR-enabled subnets.
  • Improved error resolution suggestions have been added to the UI for Cloudera AI Registry, empowering users to troubleshoot issues on their own.

Cloudera AI Inference service

  • Added support for new models, including NeMo Retriever’s GraphicElements, PageElements, and TableStructure, as well as PaddleOCR, Boltz-2, and GPT-OSS models.
  • The Test Model feature is now available for Speech-to-Text models.
  • You can now specify vLLM arguments when deploying Hugging Face models.
  • Improved error resolution suggestions have been added to the UI for Cloudera AI Inference service empowering users to troubleshoot issues on their own.
  • Grouped CPU/GPU nodes under the Cloudera AI Inference service Details page for a more user-friendly experience.

Cloudera AI Registry

  • You can now provision multiple CPU/GPU resource groups in the Cloudera AI Workbench. This provides enhanced control over workload scheduling and allows segregation of workloads based on the instance types.
  • Added support for EKS 1.32.
  • Added support for AKS 1.32.

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

Cloudera Data Flow

Cloudera Data Flow 2.11.0-b171 introduces the following changes:

New features

Latest NiFi version
Flow Deployments and Test Sessions now support the latest Apache NiFi 1.28.1 and NiFi 2.4 releases.

Service CIDR override on AWS
You can now override service CIDR (Classless Inter-Domain Routing) range settings while enabling an environment for Cloudera Data Flow on AWS.

Additional storage space for Python processors
You can now configure additional storage for Python processors during flow deployment. The wizard automatically detects if the flow definition being deployed contains any Python processors and suggests the amount of extra disk space to add because of them.

Platform updates

New Kubernetes version support
Cloudera Data Flow now supports EKS/AKS 1.32.

Azure Active Directory (AD) Pod Identity has been replaced with Azure AD Workload Identity
Cloudera Data Flow has migrated from the deprecated Azure AD Pod Identity to Azure AD Workload Identity. For more information on Azure AD Workload Identity, see this article.

Changes and improvements

Opening flows created outside Cloudera Data Flow with Flow Designer
In earlier releases, only flow definitions created in Flow Designer could be opened in Flow Designer. The reason behind this was Flow Designer’s inability to handle flows with different process groups referencing non-root parameter contexts. With the current improvements, Flow Designer is now able to open basically any flow, created anywhere. This applies both to flows being opened for editing and flows being migrated to NiFi 2.

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

Cloudera Operational Database

Cloudera Operational Database 1.54 introduces the following changes:

Enhancements to the Cloudera Operational Database UI
When you create an operational database using the Cloudera Operational Database web interface, the options previously presented under the Settings step are integrated into the Configurations step. This optimization enhances both performance and usability.

Consequently, the process of creating an operational database now comprises four distinct steps: General > Commissioning > Configurations > Review.

For more information, see Creating a database using Cloudera Operational Database.

Enhancements to the CollectDiagnostics command
The following new options are added to the CLI command, CollectDiagnostics.

  • --destination (string) : Defines the destination of the created diagnostics bundle. The supported values are UPLOAD_TO_CLOUDERA and DOWNLOAD.
  • --case-number (string) : Defines the CSH case number to be associated along with the diagnostic bundle.
  • --bundle-size-bytes (integer) : Diagnostic bundle size limit.

The following is an example of the command using the options mentioned above.

collect-diagnostics --environment-name <***ENVIRONMENT NAME***> --database-name <***DATABASE NAME***> --end-time <***END TIME***> [--start-time <***START TIME***>] [--destination <***DESTINATION***>] [--case-number <***CSH CASE NUMBER***>] [--bundle-size-bytes <***SIZE LIMIT***>] [--cli-input-json <***JSON STRING***>] [--generate-cli-skeleton]

For more information, see CDP CLI documentation.

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