A walkthrough shows how to use Octopus Deploy's AI Assistant to scaffold an orchestration project that coordinates the sequential deployment of two Kubernetes microservice projects using the Deploy a Release step. The setup includes creating a mock Kubernetes target, two identical microservice projects, and a parent orchestration project that promotes both through Development, Test, and Production environments as a single unit, while still allowing independent deployment of each child project.
Table of contents
PrerequisitesCreating the projectThe orchestration projectThe deployment processWhat just happened?Tags:Questions this post answers
How do I deploy multiple Kubernetes microservices together as a single unit in Octopus Deploy?
Create an orchestration project that uses the Deploy a Release step to trigger deployments of each child microservice project in sequence. The orchestration project promotes releases through environments like Development, Test, and Production, and when triggered, deploys each child project to the same environment, while each child project remains independently deployable outside the orchestration project. Teams coordinating multi-service Kubernetes releases can track Octopus Deploy orchestration patterns on daily.dev.
Can Octopus Deploy child projects still be deployed independently when using an orchestration project?
Yes, child projects retain full independence even when managed by an orchestration project. The Deploy a Release step can skip deploying a child project if it was already deployed to the target environment, or it can redeploy it, so teams can promote services together as a unit or deploy them separately as needed. Developers weighing coupled versus independent microservice deployments can follow this pattern on daily.dev.