9 Deploying Aspire apps to production

The chapter explains how to move a .NET Aspire application from local development into production with confidence by making a few important design adjustments first. It shows how to plan for realistic deployment needs such as multiple replicas for busy services, different behaviors for local versus cloud environments, automated database migrations, and extra operational commands in the dashboard. These changes make the system easier to scale, maintain, and operate once it is live.

It then describes how Aspire applications are prepared for deployment by generating a manifest that captures the application’s resources, dependencies, and configuration in a structured JSON format. That manifest becomes the basis for deploying to Azure Container Apps, where Azure Developer CLI can initialize the project, log in, provision infrastructure, and deploy the app. The chapter also shows how the same deployment flow can be driven from Visual Studio, how generated infrastructure files can be customized, and how the manifest can be translated into Terraform for broader cloud support.

Finally, the chapter extends the deployment story to Kubernetes by using tools that convert the Aspire manifest into Kubernetes-friendly YAML and then applying it to a cluster with kubectl. It closes by emphasizing CI/CD automation, demonstrating how to scaffold pipelines in GitHub Actions and Azure DevOps, add build and test stages before deployment, and adapt the scripts for Kubernetes-based releases. The overall message is that Aspire apps can be prepared once, then deployed and automated across multiple environments with a consistent, repeatable process.