From 6a9cb7bdf57a4246ee48e7d91d75e98f644d1396 Mon Sep 17 00:00:00 2001 From: Bob Walker Date: Thu, 8 Jan 2026 08:59:01 -0600 Subject: [PATCH 1/5] Made the fact we only support a version for six months clearer. Added it to a couple more pages. --- src/pages/docs/administration/upgrading/index.mdx | 2 +- .../self-hosted-octopus/installation-guidelines.mdx | 5 +++++ src/pages/docs/installation/index.mdx | 8 ++++---- src/pages/docs/installation/requirements.mdx | 5 +++++ .../installation/octopus-releases.include.md | 8 +++++--- 5 files changed, 20 insertions(+), 8 deletions(-) diff --git a/src/pages/docs/administration/upgrading/index.mdx b/src/pages/docs/administration/upgrading/index.mdx index 751c99681e..5ecd196d2f 100644 --- a/src/pages/docs/administration/upgrading/index.mdx +++ b/src/pages/docs/administration/upgrading/index.mdx @@ -63,7 +63,7 @@ The Windows Service is split across multiple folders to make upgrading easy and - **Tentacles**: Octopus Deploy connects to deployment targets via the Tentacle service. Each version of Octopus Deploy includes a specific Tentacle version. Tentacle upgrades do not occur until _after_ the Octopus Deploy server is upgraded. Tentacle upgrades are optional; any Tentacle greater than 4.x will work [with any modern version of Octopus Deploy](/docs/support/compatibility). We recommend you upgrade them to get the latest bug fixes and security patches when convenient. - **Calamari**: The Tentacles facilitate communication between Octopus Deploy and the deployment targets. Calamari is the software that does the actual deployments. Calamari and Octopus Deploy are coupled together. Calamari is upgraded automatically during the first deployment to a target. -## Octopus Deploy Server release schedule +## Supported Octopus Deploy Server Versions diff --git a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx index eb81c7b290..0b21262a7f 100644 --- a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx +++ b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx @@ -8,6 +8,7 @@ navOrder: 10 hideInThisSection: true --- import OctopusInstanceMixedOSWarning from 'src/shared-content/administration/octopus-instance-mixed-os-warning.include.md' +import OctopusReleases from 'src/shared-content/installation/octopus-releases.include.md'; Octopus Deploy supports two hosting options: @@ -22,6 +23,10 @@ There are three components to an Octopus Deploy instance: This document will provide you with guidelines and recommendations for self-hosting Octopus Deploy. +## Supported Octopus Deploy Server Versions + + + ## Host Octopus on Windows Server or as a Linux Container Our recommendation is to host Octopus Deploy Windows Server over the Octopus Server Linux Container unless you are okay with **all** these conditions: diff --git a/src/pages/docs/installation/index.mdx b/src/pages/docs/installation/index.mdx index cfc22015f8..13d2edd425 100644 --- a/src/pages/docs/installation/index.mdx +++ b/src/pages/docs/installation/index.mdx @@ -44,6 +44,10 @@ When installed, the self-hosted Octopus Server: Before you install Octopus Deploy, review the software and hardware [requirements](/docs/installation/requirements/), and make sure you have access to an instance of [SQL Server Database](/docs/installation/sql-server-database) that you can use with Octopus Deploy. +## Supported Octopus Deploy Server Versions + + + ## Install Octopus as a Windows Service \{#install-octopus} 1. [Download](https://Octopus.com/downloads/server) the Octopus installer. @@ -109,10 +113,6 @@ Click **Open in browser** to launch the **Octopus Web Portal** and log in using The **Octopus Web Portal** is where you'll manage your infrastructure, projects, deployment process, access the built-in repository, and manage your deployments and releases. -## Releases of Octopus Deploy Server - - - ## Learn more - [Troubleshooting the Octopus installation](/docs/installation/troubleshooting) diff --git a/src/pages/docs/installation/requirements.mdx b/src/pages/docs/installation/requirements.mdx index 95f5f64d52..f840fdbac6 100644 --- a/src/pages/docs/installation/requirements.mdx +++ b/src/pages/docs/installation/requirements.mdx @@ -6,6 +6,7 @@ title: Installation requirements description: Software and hardware requirements for installing the Octopus Server. navOrder: 1 --- +import OctopusReleases from 'src/shared-content/installation/octopus-releases.include.md'; import MinimumRequirements from 'src/shared-content/installation/minimum-requirements.include.md'; import Sql from 'src/shared-content/installation/sql.include.md'; @@ -19,6 +20,10 @@ Octopus Server can be hosted on either: However, once your Octopus Server is up and running, you can deploy to Windows servers, Linux servers, Microsoft Azure, AWS, GCP, Cloud Regions, or even an offline package drop. +## Supported Octopus Deploy Server Versions + + + ### Windows Server Octopus Server can be hosted on **Windows Server 2012 R2 or higher**. We support Octopus Server on the following versions of Windows Server: diff --git a/src/shared-content/installation/octopus-releases.include.md b/src/shared-content/installation/octopus-releases.include.md index efe83e24d7..0c0346d3a3 100644 --- a/src/shared-content/installation/octopus-releases.include.md +++ b/src/shared-content/installation/octopus-releases.include.md @@ -1,5 +1,7 @@ -From **Octopus 2020.6**, we ship a new release of Octopus Deploy Server once a quarter. Each release receives *six months support*, including critical patches. The releases are rolled out to Octopus Cloud instances before being made available to download for self-hosted instances of the Octopus Server. +Each self-hosted release of Octopus Deploy will receive critical patches and support for a period of six months. -We highly recommend using the latest release for your self-hosted installation of Octopus. Please see the [Octopus.com/downloads](https://octopus.com/downloads) page to download the latest version of Octopus Deploy. +All new releases of Octopus Deploy will run in Octopus Cloud first for at least one quarter. As a result, Octopus Cloud is always at least one version ahead of the self-hosted version. -For more details about the changes to the way we release Octopus, check out the blog post [Octopus releases and Long Term Support (LTS)](https://octopus.com/blog/releases-and-lts). \ No newline at end of file +Because of that, we always recommend using the latest available release for your self-hosted installation of Octopus. Please see the [Octopus.com/downloads](https://octopus.com/downloads) to download the latest version of Octopus Deploy. + +For more details, please refer to our [blog post announcement from 2020](https://octopus.com/blog/releases-and-lts), when we introduced this release cadence. \ No newline at end of file From 7941948acd794a702b2c0567216750179fccc301 Mon Sep 17 00:00:00 2001 From: Bob Walker Date: Thu, 8 Jan 2026 09:03:19 -0600 Subject: [PATCH 2/5] Clarifying it's a major.minor - not major.minor.patch --- src/shared-content/installation/octopus-releases.include.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/shared-content/installation/octopus-releases.include.md b/src/shared-content/installation/octopus-releases.include.md index 0c0346d3a3..30c7066091 100644 --- a/src/shared-content/installation/octopus-releases.include.md +++ b/src/shared-content/installation/octopus-releases.include.md @@ -1,4 +1,4 @@ -Each self-hosted release of Octopus Deploy will receive critical patches and support for a period of six months. +Each self-hosted major.minor release of Octopus Deploy will receive critical patches and support for a period of six months. For example, 2025.4 was released in December 2025 and will be supported for six months. All new releases of Octopus Deploy will run in Octopus Cloud first for at least one quarter. As a result, Octopus Cloud is always at least one version ahead of the self-hosted version. From db127339bc3c58054614a275a1c661b9612f6761 Mon Sep 17 00:00:00 2001 From: Bob Walker Date: Thu, 8 Jan 2026 09:09:51 -0600 Subject: [PATCH 3/5] Markdown lint fun --- .../docs/administration/upgrading/index.mdx | 4 +-- .../installation-guidelines.mdx | 9 ++--- src/pages/docs/installation/index.mdx | 36 +++++++++---------- src/pages/docs/installation/requirements.mdx | 29 +++++++-------- 4 files changed, 40 insertions(+), 38 deletions(-) diff --git a/src/pages/docs/administration/upgrading/index.mdx b/src/pages/docs/administration/upgrading/index.mdx index 5ecd196d2f..e60b9e8f74 100644 --- a/src/pages/docs/administration/upgrading/index.mdx +++ b/src/pages/docs/administration/upgrading/index.mdx @@ -25,6 +25,7 @@ Octopus Deploy connects to a SQL Server database, and can be hosted: ### Upgrade process When running on Windows, the typical (manual) upgrade process is: + - Run the MSI to install the latest binaries. - After the MSI finishes, it will close, and the **Octopus Manager** is launched to update each instance. @@ -34,11 +35,10 @@ Once the **Octopus Manager** starts the upgrade process, downtime _will_ occur. [Automating your upgrade process](/docs/administration/upgrading/guide/automate-upgrades) will help reduce the total upgrade time. Automation also mitigates risk, as all steps, including backups, will be followed. We've found companies who automate their upgrade process are much more likely to stay up to date. The smaller the delta between versions, the faster the upgrade. ::: -**Upgrades and the Service Watchdog** +#### Upgrades and the Service Watchdog If you are using the [Service Watchdog](/docs/administration/managing-infrastructure/service-watchdog), you will need to cancel it before you start your upgrade and recreate it after the upgrade is finished. Documentation on canceling the watchdog can be found [here](/docs/administration/managing-infrastructure/service-watchdog/#ServiceWatchdog-CancelingTheWatchdog). - ### Upgrading a highly available Octopus Deploy instance You are required to install the same MSI on all servers or nodes in your highly available Octopus Deploy instance. The MSI installs the updated binaries, which include the latest database upgrade scripts. Unlike the binaries, the database upgrade only needs to happen once. diff --git a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx index 0b21262a7f..a78a56220a 100644 --- a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx +++ b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx @@ -43,11 +43,12 @@ We are confident in the Octopus Server Linux Container's reliability and perform ## Create a single production instance -One question we get asked a lot is "should we have a single instance to deploy to all environments or have an Octopus Deploy instance per environment?" Unless there is a business requirement, our recommendation is to have a single instance to deploy to all environments and use Octopus Deploy's RBAC controls to manage permissions. We recommend this to avoid the maintenance overhead involved with having an instance per environment. +One question we get asked a lot is "should we have a single instance to deploy to all environments or have an Octopus Deploy instance per environment?" Unless there is a business requirement, our recommendation is to have a single instance to deploy to all environments and use Octopus Deploy's RBAC controls to manage permissions. We recommend this to avoid the maintenance overhead involved with having an instance per environment. -Of the customers who opt for an instance per environment, we see them have an instance for **development** and **test** environments with another instance for **staging** and **production** environments. +Of the customers who opt for an instance per environment, we see them have an instance for **development** and **test** environments with another instance for **staging** and **production** environments. If you chose this instance configuration, you would need a process to: + - Clone all the variable sets and project variables, and notify you when a new scoped variable is added. - Sync the deployment and runbook processes, but skip over steps assigned to **development** and **test**. - Update any user step templates to the latest version. @@ -60,7 +61,7 @@ Using the Octopus Deploy API, all of that is possible; however, it will require ## Run the Octopus Service, SQL server, and files on separate infrastructure -It is possible to run the Octopus Deploy service, SQL Server, and file storage on the same Windows Server or container orchestrator. That is not recommended for production instances of Octopus Deploy. Aside from having a single point of failure, it can lead to performance issues. +It is possible to run the Octopus Deploy service, SQL Server, and file storage on the same Windows Server or container orchestrator. That is not recommended for production instances of Octopus Deploy. Aside from having a single point of failure, it can lead to performance issues. The database should run on a dedicated SQL Server, or using a managed SQL Server like AWS RDS, or Azure SQL. The files should be stored on a NAS, SAN, or on a managed file storage platform like Azure File Storage that supports SMB/CIFS. Shared services like these are managed by dedicated individuals, such as DBAs or Network Admins. They provide common day 2 maintenance such as backups, restoring, and performance monitoring. @@ -68,7 +69,7 @@ While it is possible to run SQL Server in container, we do not recommend it for ## Use a load balancer for the Octopus Deploy UI -The Octopus Deploy UI is a stateless React single-page application that leverages a RESTful API for its data. We recommend using a load balancer for Octopus Deploy as soon as possible. This will make it much easier to move to high availability. In addition, it'll be easy to rebuild or change the underlying Windows Server or to move to Linux Containers in the future. +The Octopus Deploy UI is a stateless React single-page application that leverages a RESTful API for its data. We recommend using a load balancer for Octopus Deploy as soon as possible. This will make it much easier to move to high availability. In addition, it'll be easy to rebuild or change the underlying Windows Server or to move to Linux Containers in the future. Any standard load balancer, be it F5, Netscaler, or provided via a cloud provider, will work. If you need a small load balancer, NGINX will provide all the functionality you’ll need. diff --git a/src/pages/docs/installation/index.mdx b/src/pages/docs/installation/index.mdx index 13d2edd425..53429bb5e7 100644 --- a/src/pages/docs/installation/index.mdx +++ b/src/pages/docs/installation/index.mdx @@ -26,6 +26,7 @@ There are three components to an Octopus Deploy instance: - **Files or BLOB Storage** Some larger files - like [packages](/docs/packaging-applications/package-repositories), artifacts, and deployment task logs - aren't suitable to be stored in the database and are stored on the file system instead. This can be a local folder, a network file share, or a cloud provider's storage. All inbound traffic to Octopus Deploy is via: + - HTTP/HTTPS (ports 80/443) - Polling tentacles (port 10943) - gRPC (port 8443) @@ -50,28 +51,28 @@ Before you install Octopus Deploy, review the software and hardware [requirement ## Install Octopus as a Windows Service \{#install-octopus} -1. [Download](https://Octopus.com/downloads/server) the Octopus installer. -1. Start the Octopus Installer, click **Next**, accept the **Terms in the License Agreement** and click **Next**. -1. Accept the default **Destination Folder** or choose a different location and click **Next**. -1. Click **Install**, and give the app permission to **make changes to your device**. -1. Click **Finish** to exit the installation wizard and launch the **Getting started wizard** to configure your Octopus Server. -1. Click **Get started...** and either enter your details to start a free trial of Octopus Deploy or enter your **license key** and click **Next**. -1. Accept the default **Home Directory** or enter a location of your choice and click **Next**. -1. Decide whether to use a **Local System Account** or a **Custom Domain Account**. +- [Download](https://Octopus.com/downloads/server) the Octopus installer. +- Start the Octopus Installer, click **Next**, accept the **Terms in the License Agreement** and click **Next**. +- Accept the default **Destination Folder** or choose a different location and click **Next**. +- Click **Install**, and give the app permission to **make changes to your device**. +- Click **Finish** to exit the installation wizard and launch the **Getting started wizard** to configure your Octopus Server. +- Click **Get started...** and either enter your details to start a free trial of Octopus Deploy or enter your **license key** and click **Next**. +- Accept the default **Home Directory** or enter a location of your choice and click **Next**. +- Decide whether to use a **Local System Account** or a **Custom Domain Account**. Learn more about the [permissions required for the Octopus Windows Service](/docs/installation/permissions-for-the-octopus-windows-service/) or using a [Managed Service Account](/docs/installation/managed-service-account). -9. On the **Database** page, click the drop-down arrow in the **Server Name** field to detect the SQL Server Database. Octopus will create the database for you which is the recommended process; however, you can also [create your own database](/docs/installation/sql-server-database/#creating-the-database). -10. Enter a name for the database, and click **Next** and **OK** to **create the database**. +- On the **Database** page, click the drop-down arrow in the **Server Name** field to detect the SQL Server Database. Octopus will create the database for you which is the recommended process; however, you can also [create your own database](/docs/installation/sql-server-database/#creating-the-database). +- Enter a name for the database, and click **Next** and **OK** to **create the database**. Be careful **not** to use the name of an existing database as the setup process will install Octopus into that pre-existing database. -11. Accept the default port and directory or enter your own and click **Next**. -12. If you're using **username and passwords stored in Octopus** authentication mode, enter the username and password that will be used for the Octopus administrator. If you are using [active directory](/docs/security/authentication/active-directory), enter the active directory user details. +- Accept the default port and directory or enter your own and click **Next**. +- If you're using **username and passwords stored in Octopus** authentication mode, enter the username and password that will be used for the Octopus administrator. If you are using [active directory](/docs/security/authentication/active-directory), enter the active directory user details. You can configure additional [Authentication Providers](/docs/security/authentication) for the Octopus Server after the server has been installed. -12. Click **Install**. +- Click **Install**. When the installation has completed, click **Finish** to launch the **Octopus Manager**. @@ -115,8 +116,7 @@ The **Octopus Web Portal** is where you'll manage your infrastructure, projects ## Learn more - - [Troubleshooting the Octopus installation](/docs/installation/troubleshooting) - - [Configure your infrastructure](/docs/infrastructure) - - [Upgrading guide](/docs/administration/upgrading) - - [Automating Octopus installation](/docs/installation/automating-installation) - +- [Troubleshooting the Octopus installation](/docs/installation/troubleshooting) +- [Configure your infrastructure](/docs/infrastructure) +- [Upgrading guide](/docs/administration/upgrading) +- [Automating Octopus installation](/docs/installation/automating-installation) \ No newline at end of file diff --git a/src/pages/docs/installation/requirements.mdx b/src/pages/docs/installation/requirements.mdx index f840fdbac6..49a909d03a 100644 --- a/src/pages/docs/installation/requirements.mdx +++ b/src/pages/docs/installation/requirements.mdx @@ -15,6 +15,7 @@ If you are hosting your Octopus Server yourself, these are the minimum requireme ## Operating system Octopus Server can be hosted on either: + - A Microsoft Windows operating system - In a [Linux](/docs/installation/octopus-server-linux-container) container. @@ -67,22 +68,22 @@ Octopus Deploy works the exact same on both bare-metal machines or VMs. All it The list of hypervisors and virtual private servers include (but not limited to): - Type-1 Hypervisors - - [VMWare ESXi](https://www.vmware.com/products/esxi-and-esx.html) - - [KVM](http://www.linux-kvm.org/page/Main_Page) - - [XEN](https://xenproject.org/) - - [Hyper-V on Windows Server](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-on-windows-server) - - [RHEV](https://www.redhat.com/en/technologies/virtualization/enterprise-virtualization) + - [VMWare ESXi](https://www.vmware.com/products/esxi-and-esx.html) + - [KVM](http://www.linux-kvm.org/page/Main_Page) + - [XEN](https://xenproject.org/) + - [Hyper-V on Windows Server](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-on-windows-server) + - [RHEV](https://www.redhat.com/en/technologies/virtualization/enterprise-virtualization) - Virtual Private Server (cloud) - - AWS - - Azure - - GCP - - Oracle + - AWS + - Azure + - GCP + - Oracle - Type-2 Hypervisors - - [VMWare Workstation](https://www.vmware.com/products/workstation-pro.html) - - [VMWare Fusion](https://www.vmware.com/products/fusion.html) - - [VirtualBox](https://www.virtualbox.org/) - - [Hyper-V on Windows 10](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/) - - [Parallels](https://www.parallels.com/) + - [VMWare Workstation](https://www.vmware.com/products/workstation-pro.html) + - [VMWare Fusion](https://www.vmware.com/products/fusion.html) + - [VirtualBox](https://www.virtualbox.org/) + - [Hyper-V on Windows 10](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/) + - [Parallels](https://www.parallels.com/) Most, if not all, of those tools include documentation or pre-built images for Windows Server 2012 R2, 2016 and 2019. Please refer to their documentation on how to install and configure a Windows Server VM. From df15d777bd52a62361a7a04304d0877f915bbd65 Mon Sep 17 00:00:00 2001 From: Bob Walker Date: Thu, 8 Jan 2026 09:18:00 -0600 Subject: [PATCH 4/5] More markdown lint fun --- src/pages/docs/administration/upgrading/index.mdx | 6 +++--- .../self-hosted-octopus/installation-guidelines.mdx | 6 +++--- .../installation/octopus-releases.include.md | 9 +++++++++ 3 files changed, 15 insertions(+), 6 deletions(-) diff --git a/src/pages/docs/administration/upgrading/index.mdx b/src/pages/docs/administration/upgrading/index.mdx index e60b9e8f74..dc9eec2311 100644 --- a/src/pages/docs/administration/upgrading/index.mdx +++ b/src/pages/docs/administration/upgrading/index.mdx @@ -29,7 +29,7 @@ When running on Windows, the typical (manual) upgrade process is: - Run the MSI to install the latest binaries. - After the MSI finishes, it will close, and the **Octopus Manager** is launched to update each instance. -Once the **Octopus Manager** starts the upgrade process, downtime _will_ occur. The upgrade should take anywhere from a minute to 30 minutes to complete depending on the number of database changes, the database's size, and compute resources. A good rule of thumb is: the greater the delta between versions, the longer the downtime. An upgrade from 2019.2.1 to 2020.5.1 will generally take longer than an upgrade from 2020.4.1 to 2020.5.1. +Once the **Octopus Manager** starts the upgrade process, downtime *will* occur. The upgrade should take anywhere from a minute to 30 minutes to complete depending on the number of database changes, the database's size, and compute resources. A good rule of thumb is: the greater the delta between versions, the longer the downtime. An upgrade from 2019.2.1 to 2020.5.1 will generally take longer than an upgrade from 2020.4.1 to 2020.5.1. :::div{.hint} [Automating your upgrade process](/docs/administration/upgrading/guide/automate-upgrades) will help reduce the total upgrade time. Automation also mitigates risk, as all steps, including backups, will be followed. We've found companies who automate their upgrade process are much more likely to stay up to date. The smaller the delta between versions, the faster the upgrade. @@ -37,7 +37,7 @@ Once the **Octopus Manager** starts the upgrade process, downtime _will_ occur. #### Upgrades and the Service Watchdog -If you are using the [Service Watchdog](/docs/administration/managing-infrastructure/service-watchdog), you will need to cancel it before you start your upgrade and recreate it after the upgrade is finished. Documentation on canceling the watchdog can be found [here](/docs/administration/managing-infrastructure/service-watchdog/#ServiceWatchdog-CancelingTheWatchdog). +If you are using the [Service Watchdog](/docs/administration/managing-infrastructure/service-watchdog), you will need to cancel it before you start your upgrade and recreate it after the upgrade is finished. Please see [documentation on canceling the watchdog](/docs/administration/managing-infrastructure/service-watchdog/#ServiceWatchdog-CancelingTheWatchdog). ### Upgrading a highly available Octopus Deploy instance @@ -60,7 +60,7 @@ The Windows Service is split across multiple folders to make upgrading easy and - **Home Folder**: The home folder stores configuration, logs, and other items unique to your instance. The home folder is separate from the install location to make it easier to upgrade, downgrade, uninstall/reinstall without affecting your instance. The default location of the home folder is `C:\Octopus`. Except in rare cases, this folder is left unchanged by the upgrade process. - **Instance Information**: The Octopus Deploy Manager allows you to configure 1 to N instances per Windows Server. The **Octopus Manager** stores a list of all the instances in the `C:\ProgramData\Octopus\OctopusServer\Instances` folder. Except in rare cases, this folder is left unchanged by the upgrade process. - **Server Folders**: Logs, artifacts, packages, and event exports are too big for Octopus Deploy to store in a SQL Server database. The server folders are sub-folders in `C:\Octopus\`. Except in rare cases, these folders are left unchanged by an upgrade. -- **Tentacles**: Octopus Deploy connects to deployment targets via the Tentacle service. Each version of Octopus Deploy includes a specific Tentacle version. Tentacle upgrades do not occur until _after_ the Octopus Deploy server is upgraded. Tentacle upgrades are optional; any Tentacle greater than 4.x will work [with any modern version of Octopus Deploy](/docs/support/compatibility). We recommend you upgrade them to get the latest bug fixes and security patches when convenient. +- **Tentacles**: Octopus Deploy connects to deployment targets via the Tentacle service. Each version of Octopus Deploy includes a specific Tentacle version. Tentacle upgrades do not occur until *after* the Octopus Deploy server is upgraded. Tentacle upgrades are optional; any Tentacle greater than 4.x will work [with any modern version of Octopus Deploy](/docs/support/compatibility). We recommend you upgrade them to get the latest bug fixes and security patches when convenient. - **Calamari**: The Tentacles facilitate communication between Octopus Deploy and the deployment targets. Calamari is the software that does the actual deployments. Calamari and Octopus Deploy are coupled together. Calamari is upgraded automatically during the first deployment to a target. ## Supported Octopus Deploy Server Versions diff --git a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx index a78a56220a..81bdbe8ca1 100644 --- a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx +++ b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx @@ -35,7 +35,7 @@ Our recommendation is to host Octopus Deploy Windows Server over the Octopus Ser - You are okay running at least one [worker](/docs/infrastructure/workers) to handle tasks typically done by the Octopus Server. The Octopus Server Linux Container doesn't include PowerShell Core or Python. - You are familiar with Docker concepts, specifically around debugging containers, volume mounting, and networking. - You are comfortable with one of the underlying hosting technologies for Docker containers; Kubernetes, ACS, ECS, AKS, EKS, or Docker Swarm. -- You understand Octopus Deploy is a stateful, not a stateless application, requiring additional monitoring. +- You understand Octopus Deploy is a stateful, not a stateless application, requiring additional monitoring. @@ -95,7 +95,7 @@ The Octopus server will process additional tasks, such as applying retention pol Use the following table below as a starting point for your compute resources. You are responsible for monitoring the resources consumed and ensuring your Octopus Deploy infrastructure isn't under or over-provisioned. -| Task Cap Per Node | Windows Compute Resources | Container Compute Resources | Database on Virtual Machines | Azure DTUs | +| Task Cap Per Node | Windows Compute Resources | Container Compute Resources | Database on Virtual Machines | Azure DTUs | | ----------------- | ------------------------- | ---------------------------------- | ---------------------------- | ------------ | | 5 - 10 | 2 Cores / 4 GB RAM | 150m - 1000m / 1500 Mi - 3000 Mi | 2 Cores / 4 GB RAM | 50 DTUs | | 20 | 4 Cores / 8 GB RAM | 1000m - 2000m / 3000 Mi - 6000 Mi | 2 Cores / 8 GB RAM | 100 DTUs | @@ -105,7 +105,7 @@ Use the following table below as a starting point for your compute resources. Yo ## Use High Availability at scale -While it is possible to configure a single-node instance to process 100+ deployments concurrently, it is not something we recommend. Once you go beyond 40 concurrent deployments, we recommend using Octopus Deploy's High Availability to scale horizontally. 40 to 80 concurrent deployments per Octopus Deploy node tends to the "sweet spot" for the maximum number of concurrent deployments. +While it is possible to configure a single-node instance to process 100+ deployments concurrently, it is not something we recommend. Once you go beyond 40 concurrent deployments, we recommend using Octopus Deploy's High Availability to scale horizontally. 40 to 80 concurrent deployments per Octopus Deploy node tends to the "sweet spot" for the maximum number of concurrent deployments. Please see our [implementation guide for High Availability](/docs/best-practices/self-hosted-octopus/high-availability) for more details. diff --git a/src/shared-content/installation/octopus-releases.include.md b/src/shared-content/installation/octopus-releases.include.md index 30c7066091..62bc6eb234 100644 --- a/src/shared-content/installation/octopus-releases.include.md +++ b/src/shared-content/installation/octopus-releases.include.md @@ -1,3 +1,12 @@ +--- +layout: src/layouts/Default.astro +pubDate: 2023-01-01 +modDate: 2023-01-01 +title: octopus release and supported versions include +description: Include the octopus deploy release and supported versions +navOrder: 666 +--- + Each self-hosted major.minor release of Octopus Deploy will receive critical patches and support for a period of six months. For example, 2025.4 was released in December 2025 and will be supported for six months. All new releases of Octopus Deploy will run in Octopus Cloud first for at least one quarter. As a result, Octopus Cloud is always at least one version ahead of the self-hosted version. From aae72427a7deac9778aeb9c48f79cedaca18b29d Mon Sep 17 00:00:00 2001 From: Bob Walker Date: Thu, 8 Jan 2026 09:21:12 -0600 Subject: [PATCH 5/5] Yet even more markdown fun --- src/pages/docs/installation/index.mdx | 2 +- src/shared-content/installation/octopus-releases.include.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/docs/installation/index.mdx b/src/pages/docs/installation/index.mdx index 53429bb5e7..deced4cdfa 100644 --- a/src/pages/docs/installation/index.mdx +++ b/src/pages/docs/installation/index.mdx @@ -119,4 +119,4 @@ The **Octopus Web Portal** is where you'll manage your infrastructure, projects - [Troubleshooting the Octopus installation](/docs/installation/troubleshooting) - [Configure your infrastructure](/docs/infrastructure) - [Upgrading guide](/docs/administration/upgrading) -- [Automating Octopus installation](/docs/installation/automating-installation) \ No newline at end of file +- [Automating Octopus installation](/docs/installation/automating-installation) diff --git a/src/shared-content/installation/octopus-releases.include.md b/src/shared-content/installation/octopus-releases.include.md index 62bc6eb234..bebd69916d 100644 --- a/src/shared-content/installation/octopus-releases.include.md +++ b/src/shared-content/installation/octopus-releases.include.md @@ -13,4 +13,4 @@ All new releases of Octopus Deploy will run in Octopus Cloud first for at least Because of that, we always recommend using the latest available release for your self-hosted installation of Octopus. Please see the [Octopus.com/downloads](https://octopus.com/downloads) to download the latest version of Octopus Deploy. -For more details, please refer to our [blog post announcement from 2020](https://octopus.com/blog/releases-and-lts), when we introduced this release cadence. \ No newline at end of file +For more details, please refer to our [blog post announcement from 2020](https://octopus.com/blog/releases-and-lts), when we introduced this release cadence.