Deploy to Kubernetes
Dette indhold er ikke tilgængeligt i dit sprog endnu.
Use aspire publish or aspire deploy to take your Aspire application to Kubernetes. Aspire uses the Kubernetes-targeted environments in your AppHost to determine how each compute resource maps to Kubernetes objects, then generates Helm charts or provisions infrastructure depending on the target you choose.
To understand how Aspire deployment works across all targets, see the Deployment overview.
Choose your target
Section titled “Choose your target”Aspire supports two Kubernetes deployment targets:
Shared prerequisites
Section titled “Shared prerequisites”- Aspire prerequisites
- Aspire CLI installed
- kubectl installed and available on your
PATH - Helm installed and available on your
PATH
How Aspire maps resources to Kubernetes
Section titled “How Aspire maps resources to Kubernetes”When you publish or deploy, Aspire translates your application model into Kubernetes-native resources:
| Aspire resource | Kubernetes resource |
|---|---|
| Project resources | Deployments or StatefulSets |
| Container resources | Deployments or StatefulSets |
| Connection strings | ConfigMaps and Secrets |
| Environment variables | ConfigMaps and Secrets |
| Endpoints | Services |
| Volumes | PersistentVolumes and PersistentVolumeClaims |
Publish vs deploy
Section titled “Publish vs deploy”Both Kubernetes targets support aspire publish. The key difference is whether the target also supports aspire deploy:
| Target | aspire publish | aspire deploy |
|---|---|---|
| Kubernetes | Generates Helm charts you apply with helm or CI | Deploys to the current kubectl context using helm install |
| AKS | Generates Helm charts and Bicep infrastructure | Provisions Azure resources and deploys in a single command |
For more on the pipeline model and how publish and deploy relate, see Pipelines and app topology.