> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/deka-metal/deka-metal-deka-registry/detail-registry/resize-storage-registry.md).

# Resize Storage Registry

You as a user can adjust the registry storage quota that you use in the in the Service Portal AI. On the Service Portal AI, in the registry where the quota will be adjusted, click the three vertical buttons, and select Resize storage.

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

The Resize Storage window appears, you can set the storage size and the unit of storage capacity measurement that will be used. There are three types of storage capacity sizes available, namely MiB (Mebibyte), GiB (Gibibyte), and TiB (Tebibyte).

<figure><img src="/files/8n8Q4J84GhnzPPRcAQ3e" alt=""><figcaption></figcaption></figure>

If you have set the storage size and the unit of measurement to be used, click the Update Resize Storage button.

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


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.cloudeka.ai/deka-metal/deka-metal-deka-registry/detail-registry/resize-storage-registry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.