feat(disk-scale-down): lower the cluster disk only with --allow-disk-decrease by syndbg · Pull Request #225 · qdrant/qcloud-cli · GitHub
Skip to content

feat(disk-scale-down): lower the cluster disk only with --allow-disk-decrease - #225

Draft
syndbg wants to merge 3 commits into
mainfrom
feat/disk-scale-down
Draft

syndbg wants to merge 3 commits into
mainfrom
feat/disk-scale-down

Conversation

@syndbg

@syndbg syndbg commented Oct 19, 2026

Copy link
Copy Markdown

Adds support for disk scale down and explicitly guards against --force usage in scripts silently making "lower disk" cluster modifications. Whether that will succeed or not a detail that is not relevant to the API. Any errors returned by the API are still received by the CLI as is.

Intentionally in draft state until the API is released to prod.

Review guidelines. Can be reviewed iteratively per commit:

  1. b68ac84 API bump which includes a serverless adjustment to the fields used in tests.
  2. fa6e26b the actual addition

The new release adds `allow_additional_disk_decrease` to
`UpdateClusterRequest`, which `cluster scale` needs to lower a disk.

It also removes the REST and gRPC ports from serverless space endpoints,
so `serverless space describe` no longer prints them.
…decrease

The platform can now lower a cluster's disk, but doing so deletes the
cluster's local snapshots. `cluster scale` refused every decrease until now.

A lower `--disk` now needs the new `--allow-disk-decrease` flag.
Without it the command fails before it sends any update, also with `--force`,
so a script cannot lower the disk by accident.

With the flag, the request sets `allow_additional_disk_decrease` and the new additional disk.
The opt-in is sent only when the disk drops.
A `--disk` below the package baseline is still raised to the baseline and a package change alone
keeps the total disk.

A snapshot-loss warning prints before the prompt, and `--force` does not
skip it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant