Cloudera 7.3.1 End of Life: December 31, 2026
Cloudera 7.3.1 reaches End of Support on December 31, 2026. Cloudera's Support Lifecycle Policy lists release 7.3.1 in its "Cloudera platform (formerly, Cloudera Data Platform [CDP])" table with a GA Date of December 2024 and an EoS Date of December 2026, and says that "the projected EoS Date can be considered to be the last day of the month specified in the table." Cloudera's documentation publishes the release as Cloudera Base on premises 7.3.1, built on Cloudera Runtime 7.3.1 and managed with Cloudera Manager 7.13.1. The only other release in that table is 7.3.2, which carries the Long Term Support mark and is supported until March 31, 2032.
Cloudera's support rule, in Cloudera's words
The policy's own summary is short: "Each Major and Minor Release will be supported until the applicable End of Support Date for such release." The table of End of Support dates comes with two caveats. Future dates "are provided for planning purposes only and are subject to change, but with the expectation that dates may move later but will not move earlier," and each date is a month that "can be considered to be the last day of the month specified." So December 2026 means December 31, 2026, and the date can move later but not earlier.
The policy's Appendix 1 defines the terms. An End of Support (EoS) Date "means the last date a release will be supported, including but not limited to fixing bugs and security patches." End of Support itself "means discontinuance of eligibility for Support Services (including but not limited to any form of maintenance or service request investigation via standard support channels from Cloudera) for a Cloudera release." The appendix also describes an End of Maintenance (EoM) phase that comes before End of Support; the Cloudera platform table prints only an EoS Date for 7.3.1.
On Long Term Support, the policy says "Selected versions of the Cloudera Base on premises product will be designated as Long Term Support." In the Cloudera platform table, the 7.3.2 row carries that mark and the 7.3.1 row does not.
The Cloudera platform releases
GA and EoS months as Cloudera's table prints them, with the EoS Date converted to the last day of the month as the policy directs. Each release links to its live status page here.
| Release | GA Date (Cloudera's table) | EoS Date | Long Term Support column | Status |
|---|---|---|---|---|
| Cloudera 7.3.2 | March 2026 | March 31, 2032 | marked | Supported |
| Cloudera 7.3.1 | December 2024 | December 31, 2026 | blank | Approaching |
Older on-premises releases (the 7.1.x line, formerly CDP Private Cloud Base) sit in a separate table of Cloudera's policy and on our Cloudera Base on Premises page; the public cloud releases are on our Cloudera on cloud page.
Key dates
- December 2024: Cloudera 7.3.1 reaches GA, per Cloudera's table.
- March 2026: Cloudera 7.3.2 reaches GA, per the same table.
- December 31, 2026: End of Support for Cloudera 7.3.1. This page.
- March 31, 2032: End of Support for Cloudera 7.3.2.
What it means for an enterprise running 7.3.1
Cloudera's definition leaves little room: after the EoS Date the release is no longer eligible for Support Services, and that includes maintenance and service request investigation through standard support channels, as well as bug fixes and security patches. A 7.3.1 cluster keeps running after December 31, 2026, but problems found on it after that day are not Cloudera's to fix on that release. The policy also notes its dates are for general planning and "are not intended to supersede any of Cloudera's contractual commitments", so a specific support agreement is the document to read for anything it promises beyond this table.
The release is short-lived by Cloudera's own standards. The appendix says End of Support "will typically occur 3 years after the General Availability date"; 7.3.1 reached GA in December 2024 and its EoS Date is December 2026. A cluster that moved to 7.3.1 expecting a three-year window has less runway than it planned for.
Components that run on top of the runtime follow their own clocks. Cloudera's policy has separate tables for Cloudera Manager, Cloudera Flow Management, Cloudera Streaming and the Data Services; check each one in use before assuming the 7.3.1 date covers it.
How to check what you are running
Cloudera Manager shows the parcels in use. Cloudera's Viewing Parcel Usage page for Cloudera Manager 7.13.1 gives two ways to open it: click the parcel icon in the top navigation bar, or click Hosts in the top navigation bar, then the Parcels tab, then the Parcel Usage button. The page can be viewed by cluster or by product, and "To view the exact versions of the software running on a given host, click the square representing the host."
A Cloudera Runtime version beginning 7.3.1, including the service pack builds Cloudera numbers 7.3.1.200 (SP1), 7.3.1.400 (SP2) and 7.3.1.500 (SP3), is on the release ending December 31, 2026. Cloudera notes that the Parcel Usage page shows parcels only, not components installed as packages. Our EOL Checker and API resolve the result against the dates above.
Upgrade path to a supported release
- Pick the target. Cloudera 7.3.2 is supported until March 31, 2032 and is the release in the Cloudera platform table with the Long Term Support mark. Cloudera's version information page names Cloudera Manager 7.13.2 as the minimum Cloudera Manager version for Cloudera Base on premises 7.3.2, and for 7.3.1 including its service packs.
- Find your source row. Cloudera's supported in-place upgrade paths table lists Cloudera Base on premises 7.3.1, 7.3.1.200 SP1, 7.3.1.400 SP2 and 7.3.1.500 SP3 as certified sources for 7.3.2 with Cloudera Manager 7.13.2. For the later 7.3.2 service packs, the certified 7.3.1 source is "7.3.1.600 SP3 CHF1 or higher" with Cloudera Manager 7.13.1.600 CHF6 or higher. Cloudera adds that the listed versions "do not represent the only supported source versions", and that if a source version is not in the table you should contact Cloudera Support before upgrading.
- Back up first. Cloudera's instruction is to "create a backup of all metadata databases" before upgrading Cloudera Manager or Cloudera Runtime: the Cloudera Manager database and component databases such as Hive Metadata Server, Ranger Admin, Ranger KMS and Schema Registry. Those backups are what make a rollback possible.
- Follow the in-place upgrade guide. Cloudera's In-Place Upgrade of Cloudera Base on premises guide covers upgrading Cloudera Manager 7, then upgrading a Cloudera Runtime cluster with the Upgrade Cluster Wizard, plus Zero Downtime Upgrade and a section on rolling back from Cloudera Base on premises 7.3.1 or 7.3.2. Select a compatible Cloudera Manager version from Cloudera's Cloudera Manager Support Matrix before you start.
- Check the rest of the stack in the same pass. The upgrade guide has its own sections on upgrading the operating system, JDK upgrade path options and Python guidelines. Our EOL Checker takes the operating system and runtime versions too.
Frequently Asked Questions
When does Cloudera 7.3.1 reach end of life?
Cloudera 7.3.1 reaches End of Support on December 31, 2026. Cloudera's support lifecycle policy lists release 7.3.1 in its Cloudera platform table with a GA Date of December 2024 and an EoS Date of December 2026, and states that each projected EoS Date can be considered the last day of the month shown.
What does End of Support mean at Cloudera?
Cloudera's policy appendix defines the EoS Date as the last date a release will be supported, including but not limited to fixing bugs and security patches. End of Support itself means the release is no longer eligible for Support Services, including any form of maintenance or service request investigation through Cloudera's standard support channels.
Which Cloudera version should 7.3.1 clusters move to?
Cloudera 7.3.2. It is the only other release in the Cloudera platform table, it carries the mark in the Long Term Support column, and its EoS Date is March 2032, which under Cloudera's last-day-of-the-month rule is March 31, 2032. Cloudera's version information page names Cloudera Manager 7.13.2 as the minimum Cloudera Manager version for Cloudera Base on premises 7.3.2, and for 7.3.1 including its service packs.
Can a 7.3.1 cluster be upgraded in place to 7.3.2?
Yes. Cloudera's supported in-place upgrade paths table certifies Cloudera Base on premises 7.3.1 and its SP1, SP2 and SP3 service packs as sources for 7.3.2 with Cloudera Manager 7.13.2. For the 7.3.2 service packs the certified 7.3.1 source is 7.3.1.600 SP3 CHF1 or higher with Cloudera Manager 7.13.1.600 CHF6 or higher. Cloudera says to back up the Cloudera Manager and component metadata databases first, and to contact Cloudera Support if a source version is not listed.
How do I check which Cloudera Runtime version a cluster runs?
In Cloudera Manager, open the Parcel Usage page: click the parcel icon in the top navigation bar, or click Hosts, then the Parcels tab, then the Parcel Usage button. Clicking a host's square shows the parcel versions installed on it. A Cloudera Runtime version beginning 7.3.1 is on the release that reaches End of Support on December 31, 2026. The page covers parcels only, not components installed as packages.
Related
- Cloudera 7.3.1 — the live status page with its EOL Risk Score
- Cloudera Platform — both releases' dates
- Cloudera 7.3.2 — the upgrade target
- Cloudera Base on Premises · Cloudera on cloud · Cloudera Data Flow — the other Cloudera lines we track
- Apache Spark 4.0 end of life — why a vendor's Spark runtime follows the vendor's dates
- 2026 EOL calendar — every dated end of support this year
- Cloudera Support Lifecycle Policy — the vendor page these dates were read from
- How we verify our dates — the rules every number on this site is held to