Plans are compute-only, so you choose the root disk separately when you create an instance. CLI
v1.0.0 and later require --blockstorage-plan, --root-disk-size, and --storage-category for a
new instance. The CLI no longer accepts custom CPU, memory, or disk selections. Choose a named
compute plan.
--blockstorage-plan: the root storage tier slug. List tiers with zcp plan storage.
--root-disk-size: the root disk size in GB for that tier.
The CLI takes slugs, not display names. List compute, storage, and network plan slugs with
zcp plan vm, zcp plan storage, and zcp plan network. List storage categories with
zcp storage-category list.
Changing an instance name changes its hostname. The platform can restart a running instance or start
a stopped instance to apply that change.
CLI v1.0.0 and later require separate fixed plans for the control plane, workers, and root storage.
The root storage plan and --root-disk-size apply to every node. Use zcp plan kubernetes and
zcp plan storage to find values in the selected region.
The command zcp kubernetes scale --enable-autoscaling submits the requested worker bounds but does
not confirm that the platform added a worker. Check cluster status after the request.
zcp vm-backup schedule creates and manages recurring VM backup policies. Policies support hourly,
daily, weekly, and monthly intervals, IANA time zones, retention counts, and paused state.
Do not use everyOtherDay. The platform can persist the policy and then return an error. If that
happens, list schedules and remove any unintended policy before retrying.
zcp acl rules retrieves every API page by default. The following pagination flags are available in
v0.0.31 and later:
Flag
Description
--max-items <count>
Return at most <count> rules. If more rules remain, the response includes a continuation token.
--starting-token <token>
Resume a previous listing from its continuation token.
--page-size <count>
Set the number of rules requested in each API call. It does not cap the total result.
--no-paginate
Request one API page. It cannot be combined with the other pagination flags.
Use a continuation token only with the same VPC and ACL. The token retains its page size. When you
resume, omit --page-size or use the same value. For consistent results, resume before the ACL
rules change.
With the default table output, a continuation token is written to standard error. With -o json or
-o yaml, a listing that uses --max-items, --starting-token, or --no-paginate returns an
object with rules and, when more rules remain, next_token. A default listing keeps the existing
JSON array or YAML list output.
We use optional analytics and advertising measurement to improve the documentation and understand campaign results. Choose each preference separately. Read our privacy policy.