Using Aspir8 to deploy to Kubernetes
With .NET Aspire, we created the app model to define all the dependencies between the different resources that are used. First, in Chapter 1, you saw the Aspire manifest that’s created from an app model. This manifest file is independent of any technology where to deploy it. The Azure Developer CLI creates Bicep scripts for deploying the solution (see Chapter 6 and Chapter 8). The open source tool Aspirate (Aspir8) (see https://github.com/prom3theu5/aspirational-manifests) converts the Aspire manifest file to Docker Compose or Kubernetes with Helm charts or kustomize manifests.
You can create an Aspire manifest for every launch profile, like so:
cd Codebreaker.AppHost dotnet run --launch-profile OnPremises -- --publisher manifest --output-path onpremises-manifest.json
Our app model is defined with two different versions. One version uses cloud-native Azure services, while the other option is independent of any cloud environment....
