What's new in Cloudera Data Services on premises 1.5.5 SP1

Understand the functionalities and improvements to features of Cloudera Data Services on premises 1.5.5 SP1.

Upgrade pre-checks

A new host inspection called Host Prerequisite Inspection is added to the upgrade pre-checks. It verifies that the minimum requirements for the system configurations are met on the hosts. For more information, see Pre-upgrade checklist.

Post Upgrade Validation

This is a set of health checks added as the last step in the upgrade to verify that the upgrade was successful and the cluster is healthy. This includes verifying that the services are healthy, the hosts are upgraded to the new version, and that the Cloudera Control Plane is in a healthy state after upgrade. For the Cloudera Control Plane to be determined as good health, it will verify that RKE2, Longhorn, and Vault are healthy. It will also check that the critical pods in the Cloudera Control Plane namespace are up and running. For more information, see Upgrading Cloudera Data Services on premises using Cloudera Embedded Container Service .

SAML enhancement in Cloudera Management Console

New settings such as Signing and encryption-decryption are added in Cloudera Management Console UI. For more information, see Setting SAML as IdP.

Data Recovery Service (DRS) functionalities

Cloudera Data Services on premises 1.5.5 SP1 and higher versions provide the following DRS features:

  • You can view the Backup and Restore Manager on the Cloudera Management Console > Backup Manager > Control Plane page.
  • You can use the S3 locations in Ozone, in AWS buckets, or in both as an external backup location to back up and restore the Cloudera Control Plane.
  • DRS automatically backs up Virtual Warehouse configurations from the database along with the namespace backup. You can restore the backup, when required.

For more information, see Data Recovery Service overview.

Cloudera Embedded Container Service containerd And kubelet health tests

Implemented health test Runners for both the Ecs Server and Ecs Agent roles within the Cloudera Embedded Container Service. These runners executed by SMON on each Ecs Server and Ecs Agent to read metrics and determine the health status containerd and kubelet, which is then displayed on the Cloudera Embedded Container Service Roles page in the Cloudera Manager UI.

Metrics are collected (60 sec of interval) by process running alongside the Ecs Server and Ecs Agent process and sent to SMON.

For more details, see ECS Agent Health test and ECS Server Health tests.

For more information on enabling Ecs Server/Agent containerd health test and Ecs Server/Agent kubelet health test, see ECS Agent Health test.