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

Technical Preview release of hybrid environments

You can connect your Cloudera Data Services on premises Cloudera Control Plane with the cloud Cloudera Control Plane to initiate setup for Cloud Bursting. See Connecting on-premises Control Plane with cloud documentation.

Cloud bursting allows you to maximize existing on-premise investment by dynamically and temporarily extending the private data center into the cloud when on-premise resource utilization nears capacity. For more information, see the Hybrid Cloud documentation

Support for tainted nodes

Cloudera Embedded Container Service now automatically applies both the Kubernetes taint and label when a node profile is selected in Cloudera Manager. Admininistrators do not have to manually run the kubectl label commands to map profiles. Selecting a profile (GPU, NVMe, CDE, CAI) in Host > Configuration and running Refresh ECS now applies both the taint and label in a single step process. No manual intervention required to run the kubectl label command. For more information, see Dedicating Cloudera Embedded Container Service nodes for specific workloads.

Cloudera Data Services on premises administrator username and password policy changes

Default administrator username and password policy changes have been enabled to have stringent access across the Cloudera Control Plane systems. For more information, see Installing Cloudera Data Services on premises using Cloudera Embedded Container Service, Installing in air-gapped environment, and Installing in Internet-connected environment.

Handling Scaling issues pertaining to Logging and Diagnostic bundle collection

Performance or operational breakdowns have been reported regarding the logging and diagnostic bundle collection pipeline. Mainly due to the lack of dynamic scalability at managing a large volume of logs. For more information, see Scaling issues pertaining to Logging and Diagnostic bundle collection.

Diagnostic bundle management

You can automatically delete old Ozone logs in S3 (by retention), perform scheduled clean up of diagnostics bundles, and collect the bundle data. By deploying the diagnostics-api-service, you can configure to schedule the clearing of Ozone logs and thresholds with environment variables. For more information, see Diagnostics bundle management.

Using Proxy Protocol for Embedded Container Service installations

You can resolve client IP address masking in Cloudera Data Services on premises deployments on Cloudera Embedded Container Service. For more information, see Enabling Proxy Protocol for Embedded Container Service installation.

Managing AWS S3 compatible Credentials for Data Services on premises

You can register shared, S3-compatible object storage credentials that workloads can reuse across your Cloudera Data Services on premises deployment. As a Cloudera administrator, you can use the Cloudera Management Console to create, edit, test, and delete external accounts under the Shared Resources. For more information, see Managing AWS S3 compatible credentials for Cloudera Data Services on premises.