Ryz Labs/Migrations/Ubuntu 22.04 end of standard support
Migrations

Ubuntu 22.04 End of Standard Support: Fleet Upgrade Plan

Standard maintenance for Jammy stops in 2027, but the OS does not die then. Here is how ESM differs, where 22.04 hides, and how to reach 24.04 or 26.04.

Short answer: Ubuntu 22.04 LTS standard support ends in spring 2027 (May 2027 on the release cycle page, April 2027 in the release notes). Rebuild on 26.04 LTS where you can, or upgrade in place through 24.04.

VersionEnd of lifeStatus on November 21, 2026
Ubuntu 22.04May 2027Supported
Ubuntu 26.04May 2031Supported

Canonical's release cycle page lists the end of standard security maintenance for Ubuntu 22.04 LTS (Jammy Jellyfish) as May 2027, while the 22.04 release notes say maintenance updates run "until April 2027"; neither page names a day. That is not end of life: Expanded Security Maintenance (ESM) through Ubuntu Pro keeps patching the release until May 2032, and a paid Legacy add-on stretches it to May 2037. Our advice for most fleets is to rebuild servers, container base images and CI runners on Ubuntu 26.04 LTS, which has standard support to May 2031, and to use an in-place hop to 24.04 LTS only for hosts you cannot rebuild.

Key dates

VersionReleasedStandard support endsESM (Ubuntu Pro) endsLegacy add-on endsStatus on November 21, 2026
Ubuntu 22.04 LTSApril 21, 2022May 2027 (release notes: April 2027)May 2032May 2037In standard support, final point release 22.04.5
Ubuntu 24.04 LTSApril 25, 2024May 2029May 2034May 2039In standard support, the only in-place target from 22.04
Ubuntu 26.04 LTSApril 23, 2026May 2031May 2036May 2041In standard support, 26.04.1 out since August 27, 2026

Dates come from Canonical's official release cycle page and the per-release schedules on documentation.ubuntu.com, checked November 21, 2026. Canonical publishes these support dates to the month only, so this page does too. One more wrinkle worth knowing: the 26.04 release notes say that release is supported "until April 2031", a month earlier than the release cycle table. Plan against the earlier month in each pair and you will never be caught short.

What end of standard support means for your systems

Most runtime deadlines are a cliff: the project stops shipping fixes and that is that. Ubuntu LTS works in tiers, and the honest answer depends on which tier your packages live in.

Standard maintenance covers Main

For its first five years, an LTS release gets CVE patches for packages in the Main repository at no cost. That is the coverage that stops for 22.04 in spring 2027. Packages from the Universe repository were never part of that free promise.

ESM through Ubuntu Pro extends it

Ubuntu Pro adds ten years of security updates for Main and also covers Universe for ten years, which is why 22.04 stays patched to May 2032 for subscribed machines. Canonical splits this into two streams: esm-infra for Main packages after the five-year window, and esm-apps for Universe. Attaching a machine is one command, sudo pro attach, which prints a link and code to enter on the Ubuntu Pro site; both ESM streams are switched on by default. Pro is free for personal use on up to five machines. For business fleets, Canonical sets the terms; check its pricing directly, because we do not quote it here.

What you actually lose on an unattached 22.04 host

Without Pro, a 22.04 server after the cutoff month stops receiving security fixes for the operating system packages it depends on: OpenSSL, the kernel, OpenSSH, glibc and the rest. Your application keeps running. Nothing switches off. The risk accumulates quietly with each new advisory you cannot apply.

Why this still matters with ESM available

Find your exposure

A Jammy fleet usually turns out larger than anyone guessed, because the release hides in three different layers. Check each one.

Servers and virtual machines

Container base images

CI runners

To speed up the repository part, paste a Dockerfile, CI workflow or other manifest into the free EOL deadline radar. It returns a dated report of the operating system and runtime versions it finds, so the Jammy line and the Python 3.10 or PostgreSQL 14 lines show up together.

What changes in the upgrade

These are the version-specific changes we would check first, taken from Canonical's notes for 24.04 and the 26.04 summary for LTS users. If you are landing on 26.04, you inherit both sets.

No skipping, and the path to 26.04 has two hops

Canonical's release upgrade guide is blunt: you cannot skip releases, and LTS-to-LTS upgrades open only after the first point release of the new LTS. The 26.04 notes confirm that older systems must first reach 24.04 (or 25.10). An in-place 22.04 server therefore goes to 24.04 and then to 26.04, a path that has been available since 26.04.1 shipped on August 27, 2026. A rebuilt server or image skips all of that.

Default toolchains and language versions jump

24.04 moves the default Python from 3.10 to 3.12, PHP from 8.1 to 8.3, PostgreSQL from 14 to 16 and Ruby from 3.0 to 3.2 (which drops File.exists? and Dir.exists?). 26.04 goes further: Python 3.14, PHP 8.5, PostgreSQL 18, OpenJDK 25 as default and GCC 15.2. Anything that installs language runtimes from the Ubuntu archive will change underneath your application, so pin or vendor runtimes you are not ready to move.

APT sources and keys change format

From 24.04, Ubuntu's own sources live in deb822 format at /etc/apt/sources.list.d/ubuntu.sources, and repositories signed with RSA keys shorter than 2048 bits draw warnings. In 26.04, apt-key is removed entirely. Dockerfiles and bootstrap scripts that still pipe a vendor key into apt-key add will fail on 26.04 and need the signed-by keyring pattern.

Security defaults tighten

24.04 disables TLS 1.0, TLS 1.1 and DTLS 1.0, and restricts unprivileged user namespaces when AppArmor is installed, which can break sandboxed browsers, some build tools and rootless container setups until they get a profile. 26.04's OpenSSH 10.2p1 drops DSA signatures. Legacy clients and old SSH keys surface here.

Service restarts during unattended upgrades

On 24.04, needrestart restarts affected services during non-interactive runs such as unattended-upgrade. That is safer for patching but can bounce a stateful daemon at an awkward moment. Exclusions go in the override_rc section of /etc/needrestart/needrestart.conf.

init, cgroups and core tools in 26.04

26.04 ships systemd 259 with cgroup v1 support removed, and it is the last release that runs System V init scripts. sudo-rs becomes the default sudo (sudo-ldap is gone, so LDAP rules must move to PAM), and the Rust rewrite of coreutils provides most core commands, with GNU versions still available under a gnu prefix. Scripts that parse tool output exactly are worth a test run.

Packages that move or disappear

24.04 replaces ISC DHCP with Kea, drops the Debian awscli package in favor of the AWS snap, and no longer preinstalls LXD on Server. 26.04 moves MySQL from 8.0 to 8.4, where accounts using mysql_native_password are locked out by default unless you re-authenticate them or enable the plugin, and it switches new installs to chrony for time sync. The 24.04 notes also warn that the upgrader may remove freeradius, and that upgrading on Oracle Cloud removes ufw.

Cloud instance types and CPU baselines

From 26.04, AMD64 cloud images are built for amd64v3 by default, and Canonical drops several previous-generation instance families on AWS (including M1 to M4, C3, C4, R3 and R4) and older N1 platforms on Google Cloud. Long-lived instances on old hardware may need a new instance type, which is one more reason to rebuild rather than upgrade in place.

The upgrade plan

Phase 1: inventory and baseline

Produce one list covering hosts, images and runners, each with an owner, a role and a decision: rebuild on 26.04, upgrade in place to 24.04, attach to Pro as a bridge, or retire. Record the package set (dpkg --get-selections) and third-party sources on representative hosts, and capture service health baselines so you can compare after the move.

Phase 2: compatibility testing

Build a 26.04 variant of each base image and run your full test suite in CI against it, alongside the current Jammy build. This is where the Python, PHP, OpenSSL, apt-key and user namespace changes surface cheaply. For pets that must stay in place, clone a production disk into a test environment and run sudo do-release-upgrade there first, noting every config prompt.

Phase 3: staged rollout

Start with stateless tiers. For rebuilt services, roll out new 26.04 instances or images behind the load balancer as a canary, then shift traffic in steps. For in-place hosts, follow Canonical's sequence: sudo apt update, then sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true, reboot if /run/reboot-required exists, take a backup, then run do-release-upgrade from a console or a session that survives a dropped connection. Canonical notes that once the download finishes the process cannot be canceled, so a snapshot is your real undo button.

Phase 4: cutover and rollback

Canonical's upgrade guide describes no way back down to 22.04, so plan rollback as replacing the instance: keep the old Jammy image or a pre-upgrade snapshot until the new hosts have carried production load cleanly. For containers, rollback is redeploying the previous tag, which is why image rebuilds are the low-risk path.

Phase 5: cleanup

Re-enable or replace third-party repositories that the upgrade disabled, remove obsolete packages, retire the Jammy images from your registry and Packer templates, and detach any Pro bridge subscriptions you no longer need. Update the CI labels so nothing new gets built on 22.04.

PhaseGoalKey techniqueExit criteria
Inventory and baselineKnow every Jammy host, image and runneros-release queries, Dockerfile grep, CI label search, fleet toolingEvery item has an owner and a decision
Compatibility testingFind breakage before production doesParallel 26.04 image builds in CI; rehearsal do-release-upgrade on cloned disksTest suites green on the target release
Staged rolloutMove load graduallyCanary instances, blue-green pools, one in-place host at a timeError rates and latency match baseline
Cutover and rollbackMake the change reversibleRetained snapshots and previous image tagsOld hosts drained with no rollback needed
CleanupStop Jammy coming backRetire images, update Packer and CI labels, review Pro attachmentsZero 22.04 references in repos and registries

Risk matrix

RiskLikelihoodImpactMitigationEarly warning
Container images stay on ubuntu:22.04 after servers moveHighMediumRegistry-wide scan plus a CI check that fails on Jammy base imagesScanner reports jammy in running workloads
Default Python, PHP or PostgreSQL version change breaks the appHighHighTest on target images first; pin runtimes or move them deliberatelyImport errors or removed-function failures in CI
Third-party repo or PPA has no package for the new releaseMediumHighCheck each vendor's repo for 24.04 and 26.04 builds before schedulingapt update errors on the rehearsal host
apt-key or weak signing keys break image builds on 26.04MediumMediumSwitch to signed-by keyrings in Dockerfiles and bootstrap scriptsBuild logs show apt-key not found
User namespace restriction breaks sandboxed or rootless toolsMediumMediumAdd AppArmor profiles rather than disabling the restriction globallyPermission errors from browsers or build sandboxes
In-place upgrade stalls mid-run on a pet serverLowHighSnapshot first, rehearse on a clone, run from a console sessionUnexpected config prompts during rehearsal
Old instance type unsupported by 26.04 cloud imagesMediumMediumMap instance families before choosing in-place versus rebuildBoot failures on test launches
Pro bridge becomes permanent and the move never finishesMediumMediumAttach with an owner and a dated exit milestonePro machine count stops falling

Typical team shape

An OS move across servers, images and pipelines touches more teams than a library bump. The work splits naturally:

Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Once you say go, engineers can typically start in under two weeks. Ryz engineers work on your team, reporting to your leads, in your repos and cloud accounts. If your fleet needs broader help, our DevOps consulting teams can take the whole migration. Scope your team.

Related

FAQ

Is Ubuntu 22.04 still safe to run after standard support ends?

It depends on coverage. A 22.04 machine attached to Ubuntu Pro keeps getting security updates for Main and Universe packages through ESM until May 2032, so it is still a maintained system. An unattached machine stops getting fixes for Main after the standard window closes in spring 2027 and slowly falls behind on advisories. Container images and CI runners are usually the unattached ones, so they are where the risk concentrates.

Which version should we upgrade to?

For anything you can rebuild, go straight to Ubuntu 26.04 LTS, which has standard support to May 2031 and avoids a second move in 2029. For servers that must be upgraded in place, the tool only takes you to 24.04 LTS first, supported to May 2029, and from there to 26.04 now that its first point release is out. Pick 24.04 as a final stop only if a vendor you depend on does not yet support 26.04.

How long does the upgrade take?

The answer depends on how many hosts are pets versus rebuildable, how many container images and CI pipelines reference 22.04, how many third-party repositories you rely on, and how far your bundled runtimes have to jump. A fleet built from images with good test coverage moves quickly; hand-configured servers with vendor packages need rehearsal on each class of host.

Can we pay for extended support?

Yes. Ubuntu Pro provides Expanded Security Maintenance for 22.04 until May 2032, and the Legacy add-on can be purchased to extend coverage to May 2037. Pro is free for personal use on up to five machines; for business use, check Canonical's current terms and pricing. Treat it as a bridge for hosts you cannot move yet, with a dated plan to exit.

What does it cost to bring in engineers?

Ryz engineers start from $7,000 per month, and our published range is $7,000 to $15,000 per engineer per month, mostly mid-level to senior. We quote per team, so the total depends on how many engineers the migration needs and for how long. You get a scoped plan, a price and the names of the people before work begins.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →