# create

Create a new flexi storage in your project. This command allows you to create a new flexi storage with the specified details.

## Usage

```
cldkctl flexi storage create [flags]
```

## Aliases

```
create, add
```

## Steps

Follow the steps below to run and view the result of this command:

#### Interactive Mode

1. Run the following command in your terminal:

```
cldkctl flexi storage create 
```

2. The terminal displays the **Create Storage** form, select the **Storage Type**.

<figure><img src="/files/eJlREaM61BG9UydgkV0D" alt=""><figcaption></figcaption></figure>

3. Select the **Volume Type**, or enter the **Volume Size in GB** according to your storage requirements.
4. When prompted, choose whether to attach the storage to an instance by selecting **Yes** or **No**.

<figure><img src="/files/0SdyzJOFKhVYanczHXP8" alt=""><figcaption></figcaption></figure>

5. Enter the **Name Volume**, select the **Zone**, and choose the **Billing Type**.

<figure><img src="/files/f46n3cKMALQ2j6ZZhcCA" alt=""><figcaption></figcaption></figure>

6. Confirm the creation by selecting **Confirm**, or cancel the process by selecting **Cancel**.

<figure><img src="/files/2JD9MvCVyD1nCJ56sGE4" alt=""><figcaption></figcaption></figure>

7. Once completed successfully, the terminal displays the success message.

<figure><img src="/files/1LMUbx12b8HAsmVVcRuz" alt=""><figcaption></figcaption></figure>

#### Non-Interactive Mode

1. Provide all required values using command flags.
2. Add `--auto-confirm` or `-y` to skip confirmation prompts in non-interactive mode.
3. Run the command in your terminal.
4. Once completed successfully, the terminal displays the success message.

<figure><img src="/files/OdyVKRmdn41hah1l6Il2" alt=""><figcaption></figcaption></figure>

## Flags

{% hint style="info" %}
This command supports [global flags](/guidance-for-individual/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details
{% endhint %}

| Flag              | Shorthand | Default | Description                                 |
| ----------------- | --------- | ------- | ------------------------------------------- |
| --attach-instance |           |         | Instance name to attach (optional)          |
| --auto-confirm    | -y        | false   | Skip confirmation prompt                    |
| --billing-type    | -b        |         | Billing Type: PPU or Trial                  |
| --help            | -h        |         | Help for the create command                 |
| --interactive     | -i        | false   | Run in interactive/TUI mode                 |
| --name            | -n        |         | Volume Name                                 |
| --project         | -p        |         | Project ID for filtering storage            |
| --storage-type    |           |         | Storage Type ID                             |
| --volume-size     |           |         | Volume Size in GB                           |
| --volume-type     |           |         | Volume Type ID                              |
| --voucher-id      |           |         | Voucher ID (required if billing-type=Trial) |
| --zone            | -z        |         | Zone ID                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/cloudeka-api-list/command-reference/cldkctl-flexi/storage/create.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.