Deployments
Create, manage, and monitor container deployments on AceCloud CaaS.
List
List all container deployments in the current project.
ace deployment listAliases: ls
Example output:
NAME TYPE STATUS IMAGE REPLICAS ENDPOINT
my-app shared Running nginx:latest 2 https://my-app.example.com
api-server dedicated Running registry.io/api:v2 3 -Get / Show
Get detailed information about a deployment.
ace deployment get <deployment-name>Aliases: show, describe
Example output:
Name: my-app
Type: shared
Status: Running
Image: nginx:latest (public)
CPU: 0.5 cores
Memory: 512Mi
Replicas: 2
External Access: true
Endpoint Access: public
Ports:
http: 80 -> 80 (HTTP)
Public Endpoints:
https://my-app.example.com
Created: 2025-03-20T14:30:00ZCreate
Create a new container deployment.
Required Flags
--name
Deployment name (3-60 chars, lowercase alphanumeric with hyphens)
--image
Container image reference (e.g. nginx:latest)
Resource Flags (Shared)
--cpu
CPU cores (0.1-16.0, required for shared)
--memory
Memory allocation (e.g. 512Mi, 1Gi, required for shared)
--replicas
1
Number of replicas (1-12)
Resource Flags (Dedicated)
--type
shared
Deployment type: shared or dedicated
--flavor
Flavor name or UUID (required for dedicated)
--network-cidr
New network CIDR (e.g. 10.0.0.0/16, for dedicated)
--network-id
Existing VPC network UUID (for dedicated)
Networking Flags
--external-access
false
Enable external access (public endpoint)
--endpoint-access
public
Endpoint mode: public or protected
--cidr
CIDR blocks for protected endpoints (repeatable)
--x-forwarded-for
false
Enable X-Forwarded-For header
Port Flags
Ports can be specified in two ways:
Single port mode:
--port-name
Port name (e.g. http)
--protocol
HTTP
Protocol: HTTP, HTTPS, TCP, UDP
--container-port
Container port (1-65535)
--exposed-port
Exposed port (1-65535, defaults to container port)
Multi-port mode:
--port
Port spec in name:protocol:containerPort[:exposedPort] format (repeatable)
Note: If no port is specified, the CLI automatically adds a default port:
http:HTTP:80:80.
Other Flags
--env
Environment variable in KEY=VALUE format (repeatable)
--volume
Volume in name:mountPath:size format (repeatable, e.g. data:/data:1Gi)
--command
Container command override (repeatable for args)
--image-type
public
Image type: public or private
--image-secret
Image pull secret for private images (repeatable)
Autoscaling Flags
--autoscale
false
Enable horizontal pod autoscaling
--autoscale-min
1
Minimum replicas (1-12)
--autoscale-max
5
Maximum replicas (1-12)
--cpu-target
80
CPU utilization target percentage (1-100)
--memory-target
80
Memory utilization target percentage (1-100)
Examples
Shared deployment with public endpoint:
With environment variables and volumes:
With autoscaling:
Protected endpoint with CIDR whitelist:
Multiple ports:
Dedicated deployment with new network:
Dedicated deployment with existing VPC:
Private image with custom command:
Update
Update an existing deployment. Only the specified flags are changed; all other fields are preserved from the current deployment state.
The deployment name and type cannot be changed.
Updatable Flags
All create flags except --name and --type can be used with update. Common examples:
Important: When updating
--env,--volume, or--command, the new values replace all existing values. Make sure to include all desired values in the update command.
Delete
Delete one or more deployments.
Aliases: rm
Examples:
Restart
Restart all pods in a deployment (rolling restart).
Example:
Replicas
List the individual replica pods for a deployment.
Aliases: pods
Example output:
Global Flags
-o, --output
Output format: table (default) or json
-v, --verbose
Show full JSON request/response
--project
Override project ID
--region
Override region
Last updated