diff --git a/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-container-image.png b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-container-image.png
new file mode 100644
index 0000000000..4f4627d9a4
Binary files /dev/null and b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-container-image.png differ
diff --git a/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-worker-pool.png b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-worker-pool.png
new file mode 100644
index 0000000000..7f8c9e2d0a
Binary files /dev/null and b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-step-worker-pool.png differ
diff --git a/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-2404-pool.png b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-2404-pool.png
new file mode 100644
index 0000000000..50c2efd91c
Binary files /dev/null and b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-2404-pool.png differ
diff --git a/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-pool.png b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-pool.png
new file mode 100644
index 0000000000..da41e5802a
Binary files /dev/null and b/public/docs/img/infrastructure/workers/dynamic-worker-pools/images/ubuntu-2204-eol-ubuntu-pool.png differ
diff --git a/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-1804-end-of-life.md b/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-1804-end-of-life.md
index 3db0da46bd..9f3b330b1b 100644
--- a/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-1804-end-of-life.md
+++ b/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-1804-end-of-life.md
@@ -1,96 +1,9 @@
----
-layout: src/layouts/Default.astro
-pubDate: 2023-01-01
-modDate: 2023-01-01
-title: Ubuntu 18.04 End-of-life
-description: Describing the deprecation process of Ubuntu 18.04 Dynamic Workers.
-navOrder: 50
-hideInThisSection: true
-hideInThisSectionHeader: true
---
-
-:::div{.warning}
-Ubuntu 18.04 images are no longer available as of 3 April 2023. The details below are provided for historical reference.
-:::
-
-
-Our Ubuntu dynamic workers are being upgraded to use Ubuntu 22.04, this upgrade will result in breaking changes for users of gcloud CLI and users of .NET Core 2.1/3.1 and Ubuntu 18.04 capabilities that are not offered by the updated replacements.
-
-## What is changing?
-
-Due to the deprecation of Ubuntu 18.04, we are upgrading our dynamic workers to use Ubuntu 22.04. This change has also required upgrades of:
-* gcloud CLI from 339.0.0 to 367.0.0; and
-* .NET Core 2.1/3.1 to .NET 6.
-
-
-## Who will be impacted?
-
-Users of Octopus Cloud using Ubuntu workers and running custom scripts or community steps may be impacted as there are breaking changes between Ubuntu 18.04 and Ubuntu 22.04, and breaking changes between .NET Core 2.1/3.1 and .NET 6.
-
-Cloud customers impacted by the GCloud CLI update will be those with a deployment process which:
-
-* Has a `Run gcloud in a Script` step, which runs on the `Hosted Ubuntu` Worker Pool, which does not use an `execution container`, and the script contains calls to `gcloud`; **OR**
-* Has a `Run a Script` step, which runs on the `Hosted Ubuntu` Worker Pool, and the script contains calls to `gcloud`.
-
-### What do I need to do?
-
-Any impacted custom scripts will need to be updated to use Ubuntu 22.04 and tested to ensure your deployment process has not been impacted by the breaking changes. To mitigate the risk in this process we will be releasing the updated dynamic worker before the deprecation date so users can test against the new workers prior to migration. Please see the timeline below for the details.
-
-**Note:** All Octopus Deploy steps will work under Ubuntu 22.04 but some community steps may be impacted.
-
-## Timeline
-
-**Update 7 February 2023**
-
-The `Ubuntu 22.04` image can be found within the configuration of a worker pool:
-
-:::figure
-
-:::
-
-**Octopus preparation**
-
-| Date | Details |
-|---------------|:--------------------------------------------------------------|
-| Q4 2022 | Octopus will produce and test an Ubuntu 22.04 worker image |
-| Jan 2023 | Internal testing of existing tooling to confirm compatibility |
-
-
-**Customer action required**
-
-| Date | Details |
-|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 Feb 2023 | Ubuntu 22.04 dynamic worker will be made available for customers.
- Customers should test their impacted deployments and runbooks on an Ubuntu 22.04 worker with the aim of completing testing by the 15th of March 2023
|
-| 15 Mar 2023 | Octopus will switch over the default "Hosted Ubuntu" worker pool to use the Ubuntu 22.04 worker.
- If customers experience failed deployments or runbooks, they will be able to select the Ubuntu 18.04 worker until 3 April 2023 while they resolve any issues with running on an Ubuntu 22.04 worker |
-| 3 Apr 2023 | Ubuntu 18.04 dynamic workers will no longer be available on Octopus Cloud. |
-
-
-## FAQ
-
-### Why the deadline of 3 April 2023?
-Ubuntu 18.04 exits LTS support and will not be patched including any security vulnerability. Consequently, Octopus will not provide an unsupported Dynamic worker image.
-
-### What are the breaking changes between Ubuntu releases?
-It is not possible to give a complete and definitive answer as this depends on your use cases. Therefore, please refer to the following release notes:
-* [18.04 to 20.04 release notes](https://wiki.ubuntu.com/FocalFossa/ReleaseNotes)
-* [20.04 to 22.04 release notes](https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668)
-
-### What are the breaking changes between the .NET releases?
-It is not possible to give a complete and definitive answer as this depends on your use cases. Therefore, please refer to the following release notes:
-* [.NET Core 3.1 release notes](https://github.com/dotnet/core/tree/main/release-notes/3.1)
-* [.NET 5 release notes](https://github.com/dotnet/core/tree/main/release-notes/5.0)
-* [.NET 6 release notes](https://github.com/dotnet/core/tree/main/release-notes/6.0)
-* [.NET release types](https://learn.microsoft.com/en-us/dotnet/core/releases-and-support)
-
-### What if I experience a breaking change but I can't remediate it in time?
-There is the option to provision your own worker with Ubuntu 18.04 and selecting its worker pool for your deployment process that experience the breaking change.
-
-### Why is GCloud CLI part of this notification?
-Ubuntu 22.04 requires a later version of GCloud CLI. We have selected the earliest version on GCloud CLI that is compatible with Ubuntu 22.04 to minimize the number of breaking changes we expose our customers to. Customers can use the [GCloud 367.0.0 Release Notes](https://cloud.google.com/sdk/docs/release-notes#36700_2021-12-14) to assess whether their GCloud script steps are impacted by the breaking changes between GCloud versions 339.0.0 and 367.0.0.
-
-### Are the Windows dynamic workers affected in any way?
-This change does not impact the Windows dynamic workers.
-
-### How does this affect Execution Containers?
-Although Ubuntu 18.04 Docker images, along with [Worker Tools](/docs/infrastructure/workers/worker-tools-versioning-and-caching), can still operate on Ubuntu 22.04 dynamic workers, we will no longer provide support for the ubuntu.18.04 Worker Tools. Instead, we have introduced a new [ubuntu.22.04](https://hub.docker.com/r/octopusdeploy/worker-tools/tags?page=1&name=22.04) image, which is recommended moving forward.
-
+layout: src/layouts/Redirect.astro
+title: Redirect
+redirect: https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools
+pubDate: 2026-07-14
+navSearch: false
+navSitemap: false
+navMenu: false
+---
diff --git a/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-2204-end-of-life.md b/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-2204-end-of-life.md
new file mode 100644
index 0000000000..a48ec06971
--- /dev/null
+++ b/src/pages/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-2204-end-of-life.md
@@ -0,0 +1,112 @@
+---
+layout: src/layouts/Default.astro
+pubDate: 2026-06-18
+modDate: 2026-06-18
+title: Ubuntu 22.04 End-of-life
+description: Describing the deprecation process of Ubuntu 22.04 Dynamic Workers.
+navOrder: 50
+hideInThisSection: true
+hideInThisSectionHeader: true
+---
+
+Our Ubuntu Dynamic Workers are being upgraded to use Ubuntu 24.04. This may result in breaking changes for users of community steps or custom scripts.
+
+## What is changing?
+
+Ubuntu 22.04 is approaching the end of its standard support, so we're upgrading our dynamic workers to use Ubuntu 24.04.
+
+## Who will be impacted?
+
+Users of Octopus Cloud using Ubuntu Dynamic Workers and running custom scripts or community steps may be impacted, as there are breaking changes between Ubuntu 22.04 and Ubuntu 24.04.
+
+If you only use built-in Octopus Deploy steps, you don't need to do anything. All built-in steps work on Ubuntu 24.04. Some community steps and custom scripts may be affected.
+
+## What do I need to do?
+
+You'll need to test any impacted custom scripts on Ubuntu 24.04 and update them to make sure your deployment process isn't affected by the breaking changes.
+
+To reduce the risk during this process, we're making the Ubuntu 24.04 Dynamic Worker available before the deprecation date so you can test against the new worker before you migrate. See the timeline below for the details.
+
+If you are running custom scripts, using community steps, or using execution containers on Ubuntu workers, we recommend following the [migration guide](#migration-guide) below to test your deployments on Ubuntu 24.04 Dynamic Workers.
+
+## Timeline
+
+### Octopus preparation
+
+| Date | Details |
+|---------------|:--------------------------------------------------------------------|
+| Jun 2026 | Octopus will produce and test an Ubuntu 24.04 Dynamic Worker image. |
+
+### Customer action required
+
+| Date | Details |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 14 Jul 2026 | Ubuntu 24.04 Dynamic Worker will be made available for customers. Customers should test their impacted deployments and runbooks on an Ubuntu 24.04 worker with the aim of completing testing by September 08, 2026. |
+| 8 Sep 2026 | Octopus will switch over the default "Hosted Ubuntu" worker pool to use the Ubuntu 24.04 worker. If customers experience failed deployments or runbooks, they can select the Ubuntu 22.04 worker until October 13, 2026 while they resolve any issues. |
+| 13 Oct 2026 | Ubuntu 22.04 Dynamic Workers will no longer be available on Octopus Cloud. |
+
+## Migration Guide
+
+For each Space on your Cloud instance, find the Ubuntu Dynamic Worker Pool. The Worker Pool name is usually either `Hosted Ubuntu` or `Default Worker Pool`. Make a note of the Worker Pool name.
+
+:::figure
+
+:::
+
+For each deployment step, check whether it runs on the Ubuntu Dynamic Worker Pool you noted above.
+
+:::figure
+
+:::
+
+Create a temporary Dynamic Worker Pool targeting the `Ubuntu 24.04` image.
+
+:::figure
+
+:::
+
+Open the deployment process for your project as well as any Runbooks. Make note of any steps using execution containers as these will need additional updates.
+
+For each step that runs on an Ubuntu Dynamic Worker Pool:
+
+- Change its Worker Pool to the new Ubuntu 24.04 Worker Pool you created following the steps above.
+- If the step runs in an execution container using the `ubuntu.22.04` Worker Tools image, change the container image to `ubuntu.24.04`. Ubuntu 22.04 Docker images can still run on Ubuntu 24.04 Dynamic Workers, but the `ubuntu.22.04` Worker Tools image will no longer be supported, so we recommend moving to `ubuntu.24.04`.
+- Your step should look something like this:
+
+ :::figure
+ 
+ :::
+
+Test your deployment by deploying a new Release of your project (Snapshot for a Runbook).
+
+### Optional cleanup after 13 October 2026
+
+To avoid having two Worker Pools that both yield the same Workers, you can restore the steps back to using the original Ubuntu Dynamic Worker Pool:
+
+1. For each step that you migrated, change the Worker Pool back to the original Ubuntu Dynamic Worker Pool, which should be now running Ubuntu 24.04 Dynamic Workers.
+1. Once no steps are using the temporary Ubuntu 24.04 Worker Pool, you can delete the temporary Worker Pool.
+
+## FAQ
+
+### Why the deadline of 13 October 2026?
+
+We're bringing the deadline forward so you can start using the new Ubuntu 24.04 Dynamic Worker image sooner, rather than waiting until Ubuntu 22.04 reaches the end of its LTS support in May 2027. This date also aligns with our Windows Dynamic Worker upgrade, so customers running both don't have to plan around two separate migrations.
+
+### What are the breaking changes between Ubuntu releases?
+
+It's not possible to give a complete and definitive answer, as this depends on your use cases. Please refer to the following documents:
+
+- [Ubuntu 22.04 release notes](https://documentation.ubuntu.com/release-notes/22.04/)
+- [Ubuntu 24.04 release notes](https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890)
+
+### What if I experience a breaking change but I can't remediate it in time?
+
+You can provision your own worker with Ubuntu 22.04 and select its worker pool for the deployment process that experiences the breaking change.
+
+### Are the Windows Dynamic Workers affected in any way?
+
+The Windows Dynamic Workers are also being updated. A separate notification covers the details of that change.
+
+### How does this affect execution containers?
+
+Ubuntu 22.04 Docker images, along with [Worker Tools](/docs/infrastructure/workers/worker-tools-versioning-and-caching), can still run on Ubuntu 24.04 Dynamic Workers. We'll no longer provide support for the `ubuntu.22.04` Worker Tools image, so we recommend moving to the new `ubuntu.24.04` image.
diff --git a/src/pages/docs/notifications/dynamic-workers-ubuntu-1804-deprecation.md b/src/pages/docs/notifications/dynamic-workers-ubuntu-1804-deprecation.md
index ba588b6d34..69e3b4ffc8 100644
--- a/src/pages/docs/notifications/dynamic-workers-ubuntu-1804-deprecation.md
+++ b/src/pages/docs/notifications/dynamic-workers-ubuntu-1804-deprecation.md
@@ -1,7 +1,7 @@
---
layout: src/layouts/Redirect.astro
title: Redirect
-redirect: https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools/ubuntu-1804-end-of-life
+redirect: https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools
pubDate: 2023-01-01
navSearch: false
navSitemap: false