Cloudera on Cloud End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cloudera on Cloud versions. Dates read at the vendor's own lifecycle pages (cloudera.com). Updated at every deploy.
Every tracked Cloudera on Cloud version is past end of life; the most recent to reach it, 7.2.18, did so on September 30, 2026. The full Cloudera on Cloud lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.2.15 LTS | 7.2.15 | May 1, 2022 | Nov 30, 2023 | 1070 days past EOL | EOL |
| 7.2.16 LTS | 7.2.16 | Jan 1, 2023 | Jun 30, 2024 | 857 days past EOL | EOL |
| 7.2.17 LTS | 7.2.17 | Jun 1, 2023 | Jun 30, 2025 | 492 days past EOL | EOL |
| 7.2.18 LTS | 7.2.18 | Apr 1, 2024 | Sep 30, 2026 | 35 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cloudera-on-cloud)
Cloudera on Cloud lifecycle status — the real story
Cloudera on Cloud — formerly CDP Public Cloud — runs on the 7.2.x line, and it has the nearest deadline of any Cloudera product: 7.2.18 reached end of support in September 2026. That is the current version for most managed deployments, so this is not a legacy-estate problem; it is a this-quarter problem for teams that have not scheduled the runtime upgrade.
The earlier 7.2.x releases are long gone — 7.2.17 ended June 2025, 7.2.16 ended June 2024, 7.2.15 ended November 2023 — and the cadence tells you what to expect: roughly two years per release. Cloudera's table puts its Long Term Support check mark on every release listed here (7.2.15 through 7.2.18), and the policy page says select versions of Cloudera on cloud are designated Long Term Support; on this line the LTS releases are the ones listed, and their windows are still about two years. Cloud deployments feel maintenance-free because the infrastructure is managed, which is exactly why the runtime version underneath them tends to go unwatched until the support notice arrives.
Spark runtimes on Cloudera on Cloud follow their own schedule and are worth checking separately: Spark 2.4.8, 3.2.3 and 3.3.x are all deprecated as of September 2026, while Spark 3.5.x follows the Data Lake support policy. Cloudera publishes its lifecycle commitments at month granularity (“EoS September 2026”) rather than as exact days. The dates in this table normalise each published month to its final day, which is how Cloudera’s own support lifecycle policy reads; treat them as the end of the stated month, not as a guaranteed cut-off timestamp.
Cloudera on Cloud release and support pattern
Across the 4 release lines with a published release date, Cloudera on Cloud has shipped a new line roughly every 8 months (median interval). A line typically stays supported for about 1.8 years from its release to its end-of-life date. 4 of the 4 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 4 release lines tracked, 4 are past end of life and 0 are still within support. The newest line, 7.2.18, was released April 1, 2024.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Cloudera on Cloud end of life mean for your organization?
When a version of Cloudera on Cloud reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Cloudera on Cloud should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Cloudera on Cloud reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Cloudera on Cloud version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Cloudera on Cloud has 4 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Cloudera on Cloud is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."