Multi-node support for Polling Tentacles

Octopus Server 2026.4.6909 introduces multi-node support for Polling Tentacles in self-hosted high-availability clusters, eliminating the previous requirement for each Tentacle to poll every server node. Using a shared Redis-based queue, any cluster node can retrieve a Tentacle’s pending work and route its response back to the originating node, allowing Tentacles to use a single address or an optional TCP load balancer without risking missed deployment tasks. Messages are encrypted with the Octopus Master Key, while larger files remain in the cluster shared directory, and connectivity pages now aggregate logs across active nodes. Adoption requires the updated Octopus Server version on all nodes, a reachable Redis instance configured as a short-lived queue, a shared read/write cluster directory, and optionally a load balancer; existing Tentacle configurations can be migrated gradually.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.