Homepage

Cloudera on Cloud: May 2026 Release Summary

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

Cloudera AI

This release of Cloudera AI includes the following changes:

Cloudera AI Studios - Agent Studio - 2.3.0:

  • Workflow Evaluations interface enhancements:
    • Table view and drill-down navigation: Streamlines run comparisons and enables hierarchical tracing to identify specific failure points.
    • Real-time monitoring: Features “in-progress” status indicators and automatic dashboard refreshes once a run completes.
    • Enhanced interpretability: Provides standardized labels and refined loop detection for clearer, more consistent result analysis.
    • Cost-saving guardrails: Prevents redundant LLM-as-a-Judge runs to reduce unnecessary compute costs.

    For more information see, Managing Workflow Evaluations.

Cloudera AI Studios - RAG Studio - 2.1.0:

  • RAG Studio installation in airgapped environments: Cloudera RAG Studio now features a containerized ML Runtime Image deployment method, streamlining installation in air-gapped environments by replacing legacy source code builds. This comprehensive image is pre-packaged with all necessary dependencies, such as Python and Node.js, to enable immediate execution upon deployment. For more information see, Installing RAG Studio in Air-gapped environments.

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

Cloudera Data Flow

Cloudera Data Flow 3.1.0-b150 introduces the following changes:

New features

Latest NiFi version
NiFi 2.6.0 and NiFi 1.28.1 have been updated to the latest hotfix build.

Managing test sessions using the CLI
You can now manage Flow Designer test sessions entirely from the CDP CLI, enabling automation and scripting of your development workflows.

Test session operations are automatically rejected with a clear error message if the deployment is in a transitional state (for example., upgrading, suspending), preventing accidental state conflicts.

For a list of available commands, see Managing test sessions using the CLI.

Managing shared parameter groups using the CLI
Full lifecycle management of shared parameter groups is now available through the CLI.

You can now reference shared parameter groups by CRN alone when creating deployments, deploying flows, or updating parameter group references - no need to specify full group details.

For a list of available commands, see Managing parameter groups using the CLI.

Data Provenance for NiFi 1.x
Data Provenance is now fully enabled for NiFi 1.x flow drafts. You can access “View Data Provenance” from the context menu on processors, funnels, input ports, and output ports to inspect data lineage and troubleshoot flow behavior.

Sparkplug IIoT Processor Support
The ConsumeMQTTIIoT processor and MQTTIIoTReader controller service are now recognized as built-in components. They no longer require a custom NAR upload to use in test sessions or deployments

Platform updates

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

NGINX to Traefik ingress controller migration
Traefik has replaced NGINX as the cluster ingress controller for Cloudera Data Flow. This change improves routing capabilities and TLS handling. When you upgrade from version 3.0.0 or lower to version 3.1.0 or higher, the ingress controller is replaced without manual intervention.

Chainguard container images
Valkey and cert-manager base images have been replaced with hardened Chainguard equivalents, improving the security posture of the runtime environment.

Changes and improvements

Flow Designer responsiveness improved
Significant performance improvements for environments running multiple concurrent test sessions:

  • Referencing components now load in approximately 0.1 seconds, down from over 1 minute in large flows
  • Overall CPU usage for Flow Designer event processing reduced by 60–80% under load
  • Optimized internal caching and indexing to reduce redundant computation
  • Deployed flow update optimization

Updating a deployed flow no longer triggers unnecessary metadata computation when KPIs are not part of the update request, reducing processing overhead.

  • PostgreSQL Driver Timeout
    The database driver timeout is now externally configurable via Helm chart values. The default remains 30 seconds, but can be increased for environments with large flows that require longer operations (such as flow draft deletion in high-volume environments).

Flow Designer event housekeeping
A new hourly scheduled task automatically purges historical flow event records, retaining only the first and last events per flow to prevent unbounded database growth.

Unused inbound connection alerts
When you terminate the last flow using an inbound connection endpoint in a deployment, an informational alert is raised at the deployment level to help you avoid unnecessary cloud costs:

“You have deleted a flow from a deployment associated with an inbound connection. If this inbound connection is no longer needed, unassign it from the deployment in the Manage Deployment view to save on cloud costs.”

This alert resolves automatically when the inbound connection is unassigned.

Updated ReadyFlows

  • Kafka to Snowflake and Confluent Cloud to Snowflake ReadyFlows updated to use key-pair authentication (StandardPrivateKeyService) to comply with Snowflake’s mandatory multi-factor authentication requirement.
  • S3 to IBM watsonx ReadyFlow updated to no longer reference a default LLM model.

Cloudera Data Flow 3.1.0-h1-b2 is a hotfix release that fixes a control plane issue that is not visible to Cloudera customers.

Cloudera Data Flow 3.1.0-h2-b2 is a hotfix release that does not include new features, but a list of fixes.

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

Cloudera Data Warehouse

Cloudera Data Warehouse 1.12.4-b57 includes the following changes:

What’s new in Cloudera Data Warehouse on cloud

Migration from NGINX to Istio in Cloudera Data Warehouse on cloud
Starting with the 1.12.4 release, Cloudera Data Warehouse no longer uses the NGINX Ingress Controller for new environments. Instead, Ingress traffic is managed using the Kubernetes Gateway API with an Istio gateway controller.

For new environments created on 1.12.4 or higher, the Ingress layer is managed by Istio, and workloads from this release utilize Gateway resources instead of Ingress resources. Consequently, workloads (Hive, Impala, or Trino) with 2025.0.21.0 or earlier, which were designed to work only with Ingress resources, cannot be deployed in 1.12.4 or higher environments.

For existing environments created before 1.12.4, the NGINX Ingress Controller continues to manage ingress traffic. These environments remain compatible with the latest supported Cloudera Data Warehouse workloads that work with NGINX. There is no automatic migration of existing environments to Istio.

This change ensures long-term support and security, as the Ingress-NGINX project is being retired with only best-effort maintenance available until March 2026.

Deprecation of Unified Analytics for Impala
Starting with this release, Cloudera Data Warehouse on cloud restricts the management of legacy Impala Virtual Warehouses that use Unified Analytics. In this release, rebuilding existing Impala Virtual Warehouses enabled with Unified Analytics is disabled. This follows the earlier release where creating new Unified Analytics-enabled Virtual Warehouses was deactivated.

To provide a migration path, you can upgrade your existing Unified Analytics-enabled Impala Virtual Warehouses to the latest version using the CDP CLI. The upgrade process disables Unified Analytics and removes its related configurations while keeping all other settings. For more information, see Migrating stored Hive queries after Unified Analytics removal.

New activation pages for AWS and Azure environments
The Activate Environment page in Cloudera Data Warehouse on cloud is redesigned for AWS and Azure environment. The legacy pop-up modal screens are replaced with dedicated, full-page guided layouts. This update streamlines the activation flow into clear, intuitive steps that align with the latest Cloudera Data Warehouse navigation patterns and complete setup with minimal clicks. For more information, see Activating an AWS environment and Activating an Azure environment.

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

Cloudera Management Console

This release of Cloudera Observability introduces the following changes:

Consumption page updates
The following improvements have been introduced to the Consumption page:

  • Usage Insights
    • The Usage section is updated to show the Data Services and Premium Services separately.
    • You are able to view your usage data in line chart and pie chart additionally to the already available bar chart type.
    • New filtering experience: use the Data Services pill filter to take a deeper look at the details of a given service.
  • Cluster section
    • View the total consumed credits, runtime and cluster count of the selected Data Services and Premium Services in the cluster section.
    • Click the Data Service or Premium Service box to look at the details of specific cluster usage.
    • If Cloudera Observability is enabled for a given cluster, you can now click the cluster name that will take you to the Cloudera Observability dashboard.

For more information, see the Credit consumption and usage insights documentation.

CDP CLI commands for Cloudera Lakehouse Optimizer
You can use the CDP CLI commands to create, update, list, delete, and perform other maintenance activities on Cloudera Lakehouse Optimizer Data Hub, policies, and associations. The CDP CLI commands for Cloudera Lakehouse Optimizer are available in the “lakehouseopt” CDP CLI subcommand. For more information, see CDP CLI for Cloudera Lakehouse Optimizer.

Cloudera Observability

This release of Cloudera Observability introduces the following changes:

Real-time monitoring support for Cloudera Base on premises

The real-time monitoring premium feature now supports Cloudera Base on premises 7.1.9 SP1 CHF1 or higher. For more information, see Feature support matrix Cloudera Observability Premium.

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

Cloudera Operational Database

Cloudera Operational Database 1.60 introduces the following changes:

Enhancements to the Cloudera Operational Database UI

Previously, when working with an operational database in the Cloudera Operational Database web interface, you configured nodes by navigating to separate actions: Actions > Configure Database for worker nodes and Actions > Configure Edge Nodes for edge nodes. All node-related configurations are now centralized under the Nodes tab.

To configure worker or edge nodes, navigate to the Databases > Database Manager page, select the Nodes tab, and choose Worker or Edge node to use the respective Configure Worker Nodes or Add Edge Nodes buttons.

For more information, see Configuring a database.

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