Plan for Ubuntu 22.04 LTS EOL: April 2027 Is 13 Months Away

What the EOL Date Means for Your Infrastructure

Ubuntu 22.04 'Jammy Jellyfish' (LTS) reaches its official end of life on April 1, 2027. That’s roughly 13 months from now. For teams on annual budget cycles, this date lands squarely in the next fiscal year, so the decision about how to handle this operating system needs to be made now.

As a long-term support (LTS) release, Ubuntu 22.04 received standard security updates until September 30, 2024 (end of active support). Since then, Canonical has continued to provide security patches as part of the LTS commitment, but those patches stop completely on April 1, 2027. No new fixes, no kernel updates, no CVE remediation. Workloads remaining on 22.04 after that date will be exposed to unpatched vulnerabilities.

The latest point release in this line is 22.04.5, which includes all updates up to that point, but it does not extend the EOL date.

Why Migration Is Often Slower Than Planned

Moving off an LTS release at enterprise scale is rarely a simple upgrade in place. Common blockers include:

• Application compatibility – Legacy software may not be certified on Ubuntu 24.04 or 26.04 (the next LTS releases). Testing, re‑certification, and potential rewrites take months.
• Regulatory compliance – PCI‑DSS, SOC 2, or FedRAMP environments require validated upgrade paths and audit trails.
• Dependency chains – One package’s upgrade can force a cascade of changes. Core infrastructure like databases, containers, or orchestration tools may lag behind.
• Change windows – Many organisations can only schedule major OS upgrades during quarterly maintenance windows. With just 13 months, that might mean only two or three viable windows.

If any of these apply to your environment, a full migration by April 2027 may be unrealistic.

Comparing the Costs of Three Options

When planning next year’s budget, you have three broad paths. Each carries different costs and trade-offs.

1. Migrate to a newer LTS

• Upfront cost: Engineering time for testing, staging, cutover, and rollback plans. Also potential third‑party application licence fees if older versions can’t run on the new OS.
• Ongoing cost: Normal maintenance on the new release. This path ends all dependence on Ubuntu 22.04 but demands the most resources before the EOL deadline.

2. Vendor extended support

• Upfront cost: Usually a per‑node, per‑year subscription. Your account team can provide pricing after April 2027.
• Ongoing cost: Annual renewal. This can be expensive when multiplied across hundreds of systems, and coverage may be limited to security patches only (not feature updates).

3. Third‑party support

• Upfront cost: Typically a flat annual fee that covers all instances of the product across your estate – no per‑node pricing.
• Ongoing cost: Renewal at the same rate. Third‑party support can deliver security patches, bug fixes, and compliance assistance well past the vendor’s EOL, often at a fraction of vendor extended support costs.

A useful exercise is to request a third‑party support quote before you enter renewal negotiations with your vendor. That quote becomes a benchmark. If the vendor’s extended support price is higher, you have negotiating leverage. If it’s lower, you still know what the alternative costs.

What to Put in the Budget Request Now

Your next budget proposal should include a clear line item for “Ubuntu 22.04 LTS post‑EOL handling.” Here’s what to specify:

• Migration costs – Internal engineering hours, contractor fees, testing tooling, and potential overtime for out‑of‑window changes.
• Extended support costs – If you plan to stay on 22.04, add the vendor’s projected annual fee for the period April 2027 onward.
• Third‑party support cost – Obtain a no‑obligation quote and include it as a contingency or primary budget line.
• Risk allowance – Set aside 10–15% for unexpected compatibility issues or extended testing cycles.

By including all three paths in the budget, you give decision‑makers a range. The actual spend will depend on migration progress through the year.

Getting a Benchmark: Request a Third‑Party Support Quote

Before you accept any renewal from your vendor, get a third‑party support quote for Ubuntu 22.04 LTS. Third‑party support can keep your systems patched and compliant long after April 2027, giving you breathing room to finish migration at your own pace.

Get a no‑obligation quote and use it as a baseline in your next budget discussion.