> For the complete documentation index, see [llms.txt](https://docs.one-click.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.one-click.dev/platform/deployments.md). # Deployments ### Overview In the deployment overview, you can see the counts of: **rollouts**, **instances**, **interfaces**, **volumes**, **envs** and **secrets**. You can also see the current container image. There is also a cpu and memory usage graph for the project. (keep in mind this is a **live** usage view, for tracking usage please use something like the )

### Kubernetes Resources You can get all resources with the corresponding labels for the projectId and deploymentId set. So you can debug in your cluster if something breaks.

### Deployment settings In the project settings, you can change the project **name**, **description**, and **labels**. You can also **delete** the project from the project settings. There is also an option to use *advanced editing* mode for the project. Head over to the [CRD](/operator-manual/crd.md) section to learn more about the Operator CRD. You can also directly create a new **blueprint** from the selected project.

#### Advanced editing {% hint style="info" %} There is **no validation** on what you configure in advanced editing. Make sure you know the configuration accoring to the Operator CRD. If something breaks, you can easily **rollback** in the [Rollouts](/platform/rollouts.md). {% endhint %} With advanced editing, you can add settings to the project that are not available in the UI. You can also see the raw CRD of the deployment.

#### New blueprint from deployment With a new blueprint from the deployment, you can create a new blueprint with the same settings as the selected deployment. The only thing which is **not** copied are the **ingress** **settings**.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.one-click.dev/platform/deployments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.