Command lineCommands

Providers

The DigitalOcean accounts of the organization, on which the platform creates nodes itself. The panel does the same on the Providers tab of the organization.

Who can do it

Any member of the organization can list and show the accounts. Only an organization admin adds, changes, verifies and deletes them.

Step 1: Add a DigitalOcean account

--region is the region new nodes go to by default. The token comes from a file (--secret-file), from stdin (--secret-stdin), from the variable KCLOUD_SECRET, or kcloud asks for it. The platform checks the token with DigitalOcean before it stores it.

$ kcloud providers add ocean --region fra1 --secret-stdin < do-token.txt

Output

Added ocean as 0195a3c4-7e21-7b6d-9f40-3c81a4d2e600; its token has every scope a node needs.

A token with custom scopes needs the 19 scopes that kcloud providers add --help lists: reading regions, sizes, images, VPCs and actions, and creating, reading and deleting droplets, volumes, firewalls and tags. The platform names the missing scopes when it refuses a token.

Step 2: List the accounts

The command shows each account with its default region, its number of nodes and the state of its token at the last check.

$ kcloud providers list

Output

NAME   KIND          REGION  NODES  TOKEN  ID
ocean  digitalocean  fra1        0  ok     0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 3: Show an account

Name the account by its name or its id. The command also shows the scopes the token lacks.

$ kcloud providers show ocean

Output

FIELD           VALUE
name            ocean
kind            digitalocean
default region  fra1
nodes           0
token           ok
checked         2026-03-14T09:30:00.000Z
created         2026-03-14T09:30:00.000Z
updated         2026-03-14T09:30:00.000Z
id              0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 4: Change an account

The command changes the name (--name) or the default region (--region). With --token it asks for a new token or reads it as providers add does.

$ kcloud providers update ocean --region ams3

Output

Updated ocean.

Step 5: Check the token again

The platform checks the stored token with DigitalOcean and records the result, which kcloud providers list then shows.

$ kcloud providers verify ocean

Output

The token of ocean has every scope a node needs.

Step 6: Check the regions and sizes

The command lists the regions with volumes and the droplet sizes with at least 2 GB of memory, with their prices. The sizes are those of the default region of the account, or of the region --region names.

$ kcloud providers catalog ocean

Output

REGION  NAME             AVAILABLE
nyc1    New York 1       yes
sfo3    San Francisco 3  yes
ams3    Amsterdam 3      yes
sgp1    Singapore 1      yes
lon1    London 1         yes
nyc3    New York 3       yes
fra1 *  Frankfurt 1      yes
tor1    Toronto 1        yes
blr1    Bangalore 1      yes
syd1    Sydney 1         yes

SIZE IN FRA1  CPU  MEMORY    DISK  USD A MONTH
s-1vcpu-2gb     1    2 GB   50 GB        12.00
s-2vcpu-2gb     2    2 GB   60 GB        18.00
s-2vcpu-4gb     2    4 GB   80 GB        24.00
s-4vcpu-8gb     4    8 GB  160 GB        48.00
s-8vcpu-16gb    8   16 GB  320 GB        96.00

Step 7: Delete an account

The platform deletes only an account that no existing node was created on.

$ kcloud providers delete ocean --yes

Output

Deleted the provider account ocean.

Tools Nodes

Matches the panel at cloud.kikimora.dev.