Homepage

Cloudera on Cloud: November 2025 Release Summary

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

Cloudera Data Engineering

Cloudera Data Engineering 1.25.0 introduces the following changes:

Virtual Cluster-level suspend and resume [Technical Preview]
From Cloudera Data Engineering version 1.25.0, the Virtual Cluster-level suspend and resume feature is available, enabling you to temporarily pause one or more Cloudera Data Engineering Virtual Clusters during idle periods. This feature is supported on both AWS and Azure. Suspending a larger number of VCs can offer significant cost savings, primarily on the compute resources.

To start using the feature, you need to request the DE_ENABLE_VC_SUSPEND_RESUME entitlement.

For more information, see Overview of suspending and resuming Cloudera Data Engineering virtual clusters.

Cloudera Data Engineering Spark support for Hive Warehouse Connector
Cloudera Data Engineering offers the integration with Hive Warehouse Connector (HWC) to access and manage Hive-managed tables from Cloudera Data Engineering Spark. The HWC dependencies are built into Cloudera Data Engineering.

Through Cloudera Data Engineering Spark, you can use HWC to read data from Hive and to write data to Hive. HWC enables secure access and querying of Hive-managed tables directly from Apache Spark. To ensure secure data handling, HWC enables you to manage data access with fine-grained access control.

For more information, see Cloudera Data Engineering Spark support for Hive Warehouse Connector.

Amazon Linux distribution migration to AL2023
The OS image has been changed from AL2 to AL2023 to help you increase security and improve application performance. AL2023 optimizes boot times to decrease the interval from instance initialization to processing the customer workload. For more information, see Comparing AL2 and AL2023.

Cloudera Data Engineering performance improvement
NodeLocalDNS is a Kubernetes-supported DaemonSet that runs a local DNS cache on every node in the cluster. The deployment of NodeLocalDNS in Cloudera Data Engineering improves application reliability, as service discovery depends on DNS. Currently, NodeLocalDNS is supported for Cloudera Data Engineering services on AWS. Key benefits of deploying NodeLocalDNS:

  • Reduced latency: queries are answered from a local cache, minimizing network hops
  • Lower CoreDNS load: repeated queries are served locally, reducing load on CoreDNS
  • Improved stability: cached entries remain available even if the CoreDNS pods restart

Cloudera Data Engineering system resilience improvement
The system resilience of Cloudera Data Engineering has been increased by enhancing the high availability capabilities of the Admission Controller to help make the system more robust in unreliable networking environments.

Upgrade precheck updates
As part of the upgrade preparation workflow, a check has been introduced to ensure that the Virtual Clusters (VCs) use a Spark version that is compatible with the Data Lake version. If the Spark version used for the VCs is incompatible with the Data Lake version, the upgrade preparation fails. For example, if the Data Lake version is upgraded from 7.2.18 to 7.3.1, and any of the VCs use a Spark version lower than 3.5.4, the upgrade preparation fails.

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

Apache Airflow version upgrade to 2.11.0
The Airflow version that Cloudera Data Engineering uses is upgraded to Airflow 2.11.0 for improved security and stability. 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 November release of Cloudera Data Hub introduces the following change:

Cluster template support on ARM
With the Cloudera Runtime 7.3.1.500 Service Pack 1 (SP3) release, the following Cloudera Data Hub templates are supported on ARM:

  • Data Discovery and exploration - Spark 3
  • Data Mart
  • Real-time Data Mart - Spark 3
  • Streams Messaging

For more information about how to create Cloudera 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:

  • 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.11.2-b383 introduces the following changes:

AWS EKS 1.33 upgrade
Cloudera supports AWS Elastic Kubernetes Service (EKS) 1.33. In 1.11.2-b383 (released November 21, 2025), when you activate an Environment, Cloudera Data Warehouse automatically provisions EKS 1.33. To upgrade to EKS 1.33 from a lower 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 and might result in cluster instability or downtime. For more information about upgrading, see Upgrading an Amazon Kubernetes Service (EKS) cluster.

Improved certificate management and load balancer compatibility
Cloudera Data Warehouse AWS environment has been updated to use AWS Network Load balancer (NLB) instead of Classic Load balancer (CLB). This update is required to improve security and to upgrade to TLS 1.3, as AWS CLB doesn’t support newer versions of TLS. To further enhance end to end encryption, TLS termination is moved to Ingress Controller (Nginx) running inside the EKS cluster instead of terminating at the load balancer. As a result, Cloudera Data Warehouse AWS environments now uses Let’s Encrypt Certificate Authority (CA) for generating the TLS certificates instead of AWS ACM certificates, starting with version 1.11.2.

Note
All Cloudera Data Warehouse AWS endpoints present a Let’s Encrypt Certificate, and the same Certificate Authority (CA) must be accepted by all users accessing those endpoints.

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

Cloudera Management Console

The November release of Cloudera Management Console introduces the following change:

Automatic user sync
With the introduction of automatic user sync, changes to environment access for users will be synced to Cloudera environments automatically, and manually triggering user sync is no longer required. The rollout of this feature begins in phases starting on November 24, 2025. Users will receive updates through their individual Notification Services once the rollout is complete.

For more information, see Syncing users to environments.

Selecting Architecture for FreeIPA, Data Lake and RDS
When creating a Cloudera environment on AWS, you can select from the following architecture types during environment creation on the Cloudera UI:

  • X86_64
  • ARM64

The following limitations apply when choosing ARM architecture:

Cloudera Lakehouse Optimizer
Starting from Cloudera on cloud 7.3.1.500 and higher versions, you can use Cloudera Lakehouse Optimizer in Cloudera Management Console to automate Iceberg table maintenance tasks. Cloudera Lakehouse Optimizer is a service on Cloudera on cloud, and it provides automated Iceberg table maintenance, through Spark jobs, for Iceberg tables in Cloudera Open Data Lakehouse. It simplifies table management, improves query performance, and reduces operational costs. It is deployed in its own dedicated Data Hub in the Cloudera Open Data Lakehouse environment.

For more information, see Lakehouse Optimizer.

Cloudera Observability

The November release of Cloudera Observability introduces the following changes:

Cloudera Manager 7.13.1.500 release
The following feature and enhancements was released as part of the Cloudera Manager 7.13.1.500 release.

  • Monitor environment health and performance using Cloudera Observability Real-time monitoring
    With Cloudera Manager version 7.13.1.500 and higher, all incoming and outgoing communications from the OpenTelemetry Collector (used for telemetry data collection) are now encrypted with TLS 1.2 before leaving the node boundary.

  • Monitoring table maintenance tasks on Cloudera Observability dashboard
    You can monitor the maintenance actions of Cloudera Lakehouse Optimizer as Spark jobs on Cloudera Observability dashboard. For more information, see the Monitoring table maintenance tasks on Cloudera Observability dashboard documentation.

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

Cloudera Operational Database

Cloudera Operational Database 1.55 introduces the following changes:

View Instance Types using the Cloudera Operational Database UI
The Cloudera Operational Database web interface now provides a comprehensive Instances Overview page where you can view and find the available instance types to choose for your deployments.

On the Cloudera Operational Database web interface, click Instances to view the available instance types for the different cloud providers.

For more information, see Viewing Instance Types in Cloudera Operational Database.

Enhancements to the Cloudera Operational Database UI
When you create an operational database using the Cloudera Operational Database web interface, the Commissioning screen is renamed to Provisioning for better understanding.

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

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