Cloudera Docs

Mandatory Cluster Registration Policy

Starting with Cloudera Manager 7.13.2 SP1 (7.13.2.10000) and Cloudera Runtime 7.3.2 SP1, Cloudera requires mandatory cluster registration when you apply a Version 2 (V2) license key. Cluster registration validates your environment against your software entitlements, links your deployments directly to your account, and optimizes license resource tracking across connected and air-gapped deployments.

Registration applies to all newly created clusters and existing clusters updating to a V2 license. Connected environments perform this process automatically within Cloudera Manager, whereas air-gapped environments require manual registration through Cloudera Account 360.

Understanding V2 Licenses and Admin Controls

When you apply a new V2 license key, Cloudera Manager introduces a Cluster Registration Status section and a dedicated Cluster Registration page in the Web Console.

Applying a V2 license key requires you to register:

  • All newly created clusters.

  • All existing, active clusters managed by that Cloudera Manager instance.

  • All active clusters whenever you apply a renewed or updated V2 license key (Re-registration).

Understanding the 60-day Cluster Registration Grace Period

When you create a cluster or apply a V2 license key, Cloudera Manager initiates a 60-day registration grace period.

Consequences of Non-Registration (Locked state)

If you do not register a cluster within the 60-day grace period, or if you apply a V2 license to an existing cluster after its 60-day period ends, Cloudera Manager places the cluster into a Locked state.

While a cluster remains in a Locked state, Cloudera Manager enforces the following operational restrictions:

  • No service restarts: You cannot restart cluster services or roles.

  • No service starts: You cannot start stopped services or clusters.

  • Configuration freeze: You cannot save or deploy configuration changes across the cluster.

  • GUI management lockout: Cloudera Manager locks administrative management functions in the Web Console.

Supported Registration Methods

Cloudera Manager supports two workflow paths based on your network architecture:

  • Online Registration (Connected Environments): Cloudera Manager automatically connects directly to the Cloudera registration server to validate entitlements and complete registration in a single step (or through a single click on the Register button).

  • Offline Registration (Air-Gapped Environments): For environments without direct internet access, you export a JSON package containing non-sensitive cluster identifiers from Cloudera Manager, process it through Cloudera Account 360 from an internet-connected workstation, and import the resulting confirmation package back into Cloudera Manager.

How to Renew and Deregister Clusters

To maintain accurate entitlement records and ensure proper resource usage, review the following key lifecycle terminology and procedures:

License Renewals (Re-registering Active Clusters)

When you apply a renewed or updated V2 license key to Cloudera Manager, you must re-register all previously registered (active) clusters to associate them with the new key:

  • Connected environments: Cloudera Manager automatically contacts Cloudera servers and re-registers all managed clusters.

  • Air-Gapped environments: Administrators must perform an offline bulk registration process using Cloudera Account 360.

Deregistration and Decommissioning

To ensure accurate record-keeping and free up license entitlements for allocation to other clusters, you must explicitly deregister clusters when you decommission them:

  • Deletion Requirement: The Cluster Deregistration page in Cloudera Manager only displays clusters that you have already deleted. Active clusters do not appear on this page.

  • Resource Recovery: Completing the deregistration process releases the associated cluster entitlements on the Cloudera license server, making those nodes available for future cluster deployments.
  • Air-Gapped Support: Like registration, cluster deregistration supports both automated online workflows for connected environments and manual offline workflows for air-gapped environments.

  • Connected Environments: Deleting a cluster in Cloudera Manager automatically deregisters the cluster from Cloudera servers.

  • Air-Gapped Environments: Administrators must manually select the deleted cluster on the Cluster Deregistration page, click Offline Deregistration, process the request package in Cloudera Account 360, and import the confirmation into Cloudera Manager.