What is an un-tenanted deployment in 3.4?

Octopus Deploy 3.4 introduced multi-tenant deployments, adding a new dimension to deployment management by allowing the same release to be deployed in different environments for various tenants, each with their own set of variables, machines, and permissions. This feature is additive, meaning existing projects can continue without modification until tenants or tags are actively used, making the transition seamless for users not immediately needing this complexity. Multi-tenant deployments enable more granular control over deployment processes, allowing for specific configurations such as scoping machines to particular tenants or adding tenant-specific deployment steps, which can enhance the deployment architecture for users requiring such precision. The design choice to avoid automatically creating a default tenant helps prevent potential confusion and blockages in existing projects by keeping un-tenanted deployments straightforward. This approach aligns with Octopus Deploy's philosophy of minimizing disruption for users not ready to adopt new features while providing powerful tools for those who need them.

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.