Compute Nest supports four deployment package types — ECS images, container images, files, and Helm charts — each suited to a different deployment scenario. Choose the type that matches your service's infrastructure and runtime requirements.
What is a deployment package?
A deployment package is the artifact that carries your service software during deployment. Compute Nest manages these packages across regions with three built-in capabilities:
Replication: Deployment packages are automatically replicated to any region you select, so your service is available where your customers are.
Mapping: When a customer creates a service instance, Compute Nest automatically maps the service instance to the correct deployment package for that region.
Permission management: The public or private visibility of a service determines the visibility of its associated deployment packages.
Choose a deployment package type
| Package type | Best for | Network requirement |
|---|---|---|
| ECS image | ECS-based deployments | No internet required |
| Container image | Docker container deployments | Internet required |
| File | Script-based deployments needing software downloads | No internet required (uses internal network) |
| Helm chart | Complex Kubernetes services managed by Helm | Internet required |
ECS image deployment package
Use an ECS image deployment package when deploying on Elastic Compute Service (ECS). Pack your software and runtime environment into the image so the deployment starts fast and does not depend on internet access.
Compute Nest replicates the image from its source region to other regions and makes it public for all users.
For more information, see ECS image deployment packages.
Container image deployment package
Use a container image deployment package when your service runs as a Docker container. Compute Nest hosts all container image packages in a public Alibaba Cloud Container Registry repository, with multiple tenants' packages isolated by namespace.
To upload your image, use a temporary key. When a customer creates a service instance, Compute Nest uses a temporary key to pull the image from the registry.
Container image packages require internet access. The ECS instances or Container Service for Kubernetes (ACK) clusters running your service must be able to reach the internet. Because images are pulled using a temporary key, this package type supports one-time deployments only — it does not support scaling or workloads that pull images dynamically.
For more information, see Manage container image deployment packages.
File deployment package
Use a file deployment package when your script-based deployment needs to download software resources. Large files can time out, and some environments have no internet access — file deployment packages solve both problems.
Compute Nest maintains one Object Storage Service (OSS) bucket per region. After you upload your files, Compute Nest copies them to every regional bucket. During deployment, a script downloads files from an internal HTTP address that Compute Nest generates for each file in the regional bucket. Downloads over the internal network are faster, more stable, and more secure than downloads over the internet.
For more information, see File deployment packages.
Helm chart deployment package
Use a Helm chart deployment package when your service has a complex structure that you manage with Helm YAML files. Helm chart packages are stored in the public Container Registry repository of Compute Nest. Upload your local Helm chart using a temporary key, and Compute Nest makes it available for pulling over the internet with a temporary key.
For more information, see Helm chart deployment packages.