> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glissando.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Capacity

> When the cluster has no room for an app's pods, and how to add capacity.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

A diagnosis links here when pods stay **Pending** because no node has enough free CPU or memory, for example:

```text theme={null}
2 of 3 api pods are Pending: no node has 512Mi of free memory. This is a cluster capacity problem, not the app's.
```

**If you are a builder:** this is not your app's problem, and your AI cannot fix it. Tell your IT team or the maintainer named in the diagnosis.

**If you maintain the platform:** raise the node group's maximum size, or add capacity through a platform release. Check whether one app's requests grew unexpectedly before adding nodes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.