Generating Manifests and Secrets
Kustomize (Default, Aspir8 managed deployments)
Navigate to your Aspire project's AppHost directory, and run:
This command (by default) will also build selected projects, and push the containers to the registry (if specified), or the local docker daemon. Builds can be skipped by passing the --skip-build flag.
Your manifests will be in the ./aspirate-output directory by default.
Compose
The output format of the manifest can also be changed to compose to generate a lightweight deployment (docker/podman compose). Secrets are not yet supported in docker compose mode. To generate a docker compose deployment, run:
Your docker-compose file will be at the path ./aspirate-output/docker-compose.yaml directory by default.
When using the --output-format compose flag, you can also build certain dockerfiles using the compose file. This will skip the build and push in Aspirate. To do this, include the --compose-build flag one or more times.
This will build the hamburger and fries dockerfiles using the compose file.
Compose is what's classed as an "Ejected Deployment" and is not managed by Aspirate when you run it.
Helm Chart
You also have the option of generating a helm chart by changing the output format to helm. To generate a helm chart, run:
Helm supports secrets, just like kustomize does, and so you will have to unlock them if you are moving between kustomize and helm.
a Helm chart is what's classed as an "Ejected Deployment" and is not managed by Aspirate when you run it.
Cli Options (Optional)
Option | Alias | Environmental Variable Counterpart | Description |
|---|---|---|---|
--project-path | -p |
| The path to the aspire project. |
--aspire-manifest | -m |
| The aspire manifest file to use |
--output-path | -o |
| The path to the output directory. Defaults to |
--skip-build |
| Skips build and Push of containers. | |
--disable-state |
| Disable aspirate state management. | |
--namespace |
| Generates a Kubernetes Namespace resource, and applies the namespace to all generated resources. Will be used at deployment time. | |
--skip-final | -sf |
| Skips The final generation of the kustomize manifest, which is the parent top level file |
--container-image-tag | -ct |
| The Container Image Tag to use as the fall-back value for all containers. |
--container-registry | -cr |
| The Container Registry to use as the fall-back value for all containers. |
--container-repository-prefix |
| The Container Repository Prefix to use as the fall-back value for all containers. | |
--container-builder |
| The Container Builder: can be | |
--image-pull-policy |
| The image pull policy to use for all containers in generated manifests. Can be | |
--disable-secrets |
| Disables secrets management features. | |
--output-format |
| Sets the output manifest format. Defaults to | |
--runtime-identifier |
| Sets the runtime identifier for project builds. Defaults to | |
--secret-password |
| If using secrets, or you have a secret file - Specify the password to decrypt them | |
--non-interactive |
| Disables interactive mode for the command | |
--private-registry |
| Enables usage of a private registry - which will produce image pull secret. | |
--private-registry-url |
| The url for the private registry | |
--private-registry-username |
| The username for the private registry. This is required if passing | |
--private-registry-password |
| The password for the private registry. This is required if passing | |
--private-registry-email |
| The email for the private registry. This is purely optional and will default to | |
--include-dashboard |
| Boolean flag to specify if the Aspire dashboard should also be included in deployments. | |
--compose-build | Can be included one or more times to set certain dockerfile resource building to be handled by the compose file. This will skip build and push in aspirate. | ||
--launch-profile | -lp | 'ASPIRATE_LAUNCH_PROFILE' | The launch profile to use when building the Aspire Manifest. |