sincecutoff.com
← all changes

bk cluster commands create, update, and delete clusters

Introduced 2026-03-31 · score 0.98

HOW TO USE IT

When creating a cluster, run `bk cluster create` with a name; to change or remove one, run `bk cluster update` or `bk cluster delete` with its UUID. Updates require at least one supported field, and the UUID is a positional argument, not a `--cluster-uuid` flag.

bk cluster create --name "<cluster-name>"
bk cluster update <cluster-uuid> --name "<new-name>"
bk cluster delete <cluster-uuid>

WHY THIS HELPS

Create, update, or delete a Buildkite cluster from the CLI.

BEFORE THIS CHANGE

The release note says the CLI supported read actions only before this change.

REQUIREMENTS AND LIMITATIONS

  • Version: v3.33.0
  • create --name STRING (required): Name of the cluster.
  • create --description STRING: Description of the cluster.
  • create --emoji STRING: Emoji for the cluster.
  • create --color STRING: Cluster color as a hex code.
  • update <cluster-uuid> (required): UUID of the cluster to update; positional argument.
  • update --name STRING: New cluster name; update requires at least one supported update field.
  • update --description STRING: New cluster description; update requires at least one supported update field.
  • update --emoji STRING: New cluster emoji; update requires at least one supported update field.
  • update --color STRING: New cluster color as a hex code; update requires at least one supported update field.
  • update --default-queue-id STRING: UUID of the queue to set as the cluster default; update requires at least one supported update field.
  • delete <cluster-uuid> (required): UUID of the cluster to delete; positional argument.
  • Prerequisite: The CLI must have valid Buildkite configuration; the command validates configuration before running.
  • Prerequisite: Authenticate and configure the CLI for a Buildkite organization before use.
  • Docs conflict: The card describes `--cluster-uuid` as a persistent flag. In v3.33.0 source, update and delete take the cluster UUID as a positional argument; no `--cluster-uuid` flag is documented there.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card