`clusters`¶

The clusters command lets you manage cluster products.

Tip

Be careful when specifying passwords on the command line. Some non-alphanumeric characters may be interpreted in an unexpected way by your shell. Use string delimitation and escape characters as needed.

Usage: croud clusters [-h]
                      {get,list,deploy,scale,upgrade,delete,restart-node,set-deletion-protection,set-ip-whitelist}
                      ...

`clusters list`¶

Usage: croud clusters list [-h] [-p PROJECT_ID] [--region REGION]
                           [--output-fmt {table,wide,json,yaml}] [--sudo]

Optional Arguments¶

-p, --project-id

The project ID to use.

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters list
+--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------+
| id                                   | name                   | numNodes | crateVersion | projectId                            | username    | fqdn                                             |
|--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | my-first-crate-cluster |        1 | 4.5.1        | 952cd102-91c1-4837-962a-12ecb71a6ba8 | default     | my-first-crate-cluster.eastus.azure.cratedb.net. |
+--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------+

`clusters deploy`¶

Usage: croud clusters deploy [-h] --product-name PRODUCT_NAME --tier TIER
                             [--unit UNIT] -p PROJECT_ID --cluster-name
                             CLUSTER_NAME --version VERSION --username
                             USERNAME --password PASSWORD
                             [--channel {stable,testing,nightly}]
                             [--cpus CPUS] [--disks DISKS]
                             [--disk-size-gb DISK_SIZE_GB]
                             [--disk-type {premium,standard}]
                             [--memory-size-mb MEMORY_SIZE_MB]
                             [--region REGION]
                             [--output-fmt {table,wide,json,yaml}] [--sudo]

Required Arguments¶

--product-name: The product name to use.
--tier: The product tier to use.
-p, --project-id: The project ID to use.
--cluster-name: The CrateDB cluster name to use.
--version: The CrateDB version to use.
--username: The CrateDB username to use.
--password: The CrateDB password to use.

Optional Arguments¶

--unit

The product scale unit to use.

--channel

Possible choices: stable, testing, nightly

The channel of the CrateDB version (superusers only).

Default: “stable”

--cpus

Number of CPU cores to allocate. Can be fractional. CrateDB Edge regions only.

--disks

Number of disks to attach. CrateDB Edge regions only.

--disk-size-gb

Size of disks to attach (in GiB). CrateDB Edge regions only.

--disk-type

Possible choices: premium, standard

Type of disks to use. CrateDB Edge regions only.

--memory-size-mb

Amount of memory to allocate (in MiB). CrateDB Edge regions only.

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters deploy \
    --product-name cratedb.az1 \
    --tier xs \
    --cluster-name my-first-crate-cluster \
    --project-id 952cd102-91c1-4837-962a-12ecb71a6ba8 \
    --version 4.5.1 \
    --username default \
    --password "s3cr3t!"
+--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------+
| id                                   | name                   | numNodes | crateVersion | projectId                            | username    | fqdn                                             |
|--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | my-first-crate-cluster |        1 | 4.5.1        | 952cd102-91c1-4837-962a-12ecb71a6ba8 | default     | my-first-crate-cluster.eastus.azure.cratedb.net. |
+--------------------------------------+------------------------+----------+--------------+--------------------------------------+-------------+--------------------------------------------------+
==> Success: Cluster deployed. It may take a few minutes to complete the changes.

Note

This command is only available for superusers.

To deploy a cluster please use the CrateDB Cloud Console.

`clusters scale`¶

Usage: croud clusters scale [-h] --cluster-id CLUSTER_ID --unit UNIT
                            [--region REGION]
                            [--output-fmt {table,wide,json,yaml}] [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.
--unit: The product scale unit to use.

Optional Arguments¶

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters scale \
    --project-id 952cd102-91c1-4837-962a-12ecb71a6ba8 \
    --cluster-id 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 \
    --unit 1
+--------------------------------------+------------------------+----------+
| id                                   | name                   | numNodes |
|--------------------------------------+------------------------+----------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | my-first-crate-cluster |        5 |
+--------------------------------------+------------------------+----------+
==> Success: Cluster scaled. It may take a few minutes to complete the changes.

`clusters upgrade`¶

Usage: croud clusters upgrade [-h] --cluster-id CLUSTER_ID --version VERSION
                              [--region REGION]
                              [--output-fmt {table,wide,json,yaml}] [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.
--version: The CrateDB version to use.

Optional Arguments¶

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters upgrade \
    --cluster-id 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 \
    --version 4.5.1
+--------------------------------------+------------------------+---------------+
| id                                   | name                   | crate_version |
|--------------------------------------+------------------------+---------------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | my-first-crate-cluster |         4.5.1 |
+--------------------------------------+------------------------+---------------+
==> Success: Cluster upgraded. It may take a few minutes to complete the changes.

Note

This command will wait for the cluster upgrade to finish or fail.

`clusters delete`¶

Usage: croud clusters delete [-h] --cluster-id CLUSTER_ID [-y]
                             [--region REGION]
                             [--output-fmt {table,wide,json,yaml}] [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.

Optional Arguments¶

-y, --yes

Default: False

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters delete \
    --cluster-id dc40090f-e1df-4974-b751-9fc27c824368
Are you sure you want to delete the cluster? [yN] y
==> Success: Cluster deleted.

Note

After deleting a cluster, existing backups will remain for 30 days since the last time a backup was made. While you won’t be able to restore these backups yourself, you can reach out to our support to have them restore a backup for you.

If you want a more recent backup, there are several options:

Create an AWS S3 repository with a base_path of /<project_id>/<cluster_id>/<name>. <project_id> and <cluster_id> refer to the “dashed” form of the corresponding ID (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). <name> can be any alphanumeric string. Afterwards, create a snapshot in your repository.
Alternatively, you can create a backup as documented in the CrateDB documentation about snapshots on repositories and snapshots by e.g. providing your own AWS S3 bucket and credentials.
Lastly, the COPY TO SQL statement can be used to export a table to an AWS S3 bucket as well.

Important

When you provide your own external storage, please ensure that the location is not world readable or writable to prevent unauthorized access to your data!

`clusters restart-node`¶

Usage: croud clusters restart-node [-h] --cluster-id CLUSTER_ID --ordinal
                                   ORDINAL [--region REGION]
                                   [--output-fmt {table,wide,json,yaml}]
                                   [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.
--ordinal: The ordinal index of the node to restart.

Optional Arguments¶

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters restart-node \
    --cluster-id 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 \
    --ordinal 1
    --sudo
+--------+----------+
|   code | status   |
|--------+----------|
|    200 | Success  |
+--------+----------+
==> Success: Node restarted. It may take a few minutes to complete the changes.

Note

This command is only available for superusers.

`clusters set-deletion-protection`¶

Usage: croud clusters set-deletion-protection [-h] --cluster-id CLUSTER_ID
                                              --value VALUE [--region REGION]
                                              [--output-fmt {table,wide,json,yaml}]
                                              [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.
--value: The deletion protection status

Optional Arguments¶

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters set-deletion-protection \
    --cluster-id 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 \
    --value true
+--------------------------------------+------------------------+----------------------+
| id                                   | name                   | deletion_protected   |
|--------------------------------------+------------------------+----------------------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | my-first-crate-cluster | TRUE                 |
+--------------------------------------+------------------------+----------------------+
==> Success: Cluster deletion protection status successfully updated

Note

This command is only available for superusers and organization admins.

`clusters set-ip-whitelist`¶

Usage: croud clusters set-ip-whitelist [-h] --cluster-id CLUSTER_ID --net NET
                                       [-y] [--region REGION]
                                       [--output-fmt {table,wide,json,yaml}]
                                       [--sudo]

Required Arguments¶

--cluster-id: The CrateDB cluster ID to use.
--net: IP Network list in CIDR format (comma-separated).

Optional Arguments¶

-y, --yes

Default: False

--region, -r

Temporarily use the specified region that command will be run in.

--output-fmt, --format, -o

Possible choices: table, wide, json, yaml

Change the formatting of the output.

--sudo

Run the given command as superuser.

Default: False

Example¶

sh$ croud clusters set-ip-whitelist \
    --cluster-id 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 \
    --net "10.1.2.0/24,192.168.1.0/24"
This will overwrite all existing CIDR restrictions. Continue? [yN] y
+--------------------------------------+---------------+-------------------------------------------------------------------------------------------------+
| id                                   | name          | ip_whitelist                                                                                    |
|--------------------------------------+---------------+-------------------------------------------------------------------------------------------------|
| 8d6a7c3c-61d5-11e9-a639-34e12d2331a1 | romanas-nosub | [{"cidr": "10.1.2.0/24", "description": null}, {"cidr": "192.168.1.0/24", "description": null}] |
+--------------------------------------+---------------+-------------------------------------------------------------------------------------------------+
==> Success: IP Network whitelist successfully updated

Feedback

New issue Edit on GitHub View on GitHub

`clusters`¶

`clusters list`¶

Optional Arguments¶

Example¶

`clusters deploy`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters scale`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters upgrade`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters delete`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters restart-node`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters set-deletion-protection`¶

Required Arguments¶

Optional Arguments¶

Example¶

`clusters set-ip-whitelist`¶

Required Arguments¶

Optional Arguments¶

Example¶

Feedback

Product

Customers

Resources

Developers

Company

Follow us

clusters¶

clusters list¶

Optional Arguments¶

Example¶

clusters deploy¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters scale¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters upgrade¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters delete¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters restart-node¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters set-deletion-protection¶

Required Arguments¶

Optional Arguments¶

Example¶

clusters set-ip-whitelist¶

Required Arguments¶

Optional Arguments¶

Example¶

Feedback

Product

Customers

Resources

Developers

Company

`clusters`¶

`clusters list`¶

`clusters deploy`¶

`clusters scale`¶

`clusters upgrade`¶

`clusters delete`¶

`clusters restart-node`¶

`clusters set-deletion-protection`¶

`clusters set-ip-whitelist`¶