> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/tools/twistcli-console-install.md).

# Install Console with twistcli

When twistcli installs Console into a Kubernetes or OpenShift cluster, it executes a series of steps. To help you troubleshoot issues when twistcli fails, the steps in the install flow are described here:

When you run `twistcli console install`, it:

1. Loads the Console image on localhost, and tags it with the registry address.
2. Deletes the old Console replication controller, if it exists, and waits for Console deletion.
3. Deletes the config map, if it exists.
4. Creates Prisma Cloud namespace, if it does not exist.
5. If the service does not exist, twistcli resolves the service template to a file and creates a new service.
6. If persistent volume claim (PVC) does not exist, twistcli resolves the PVC template to a file and creates a new PVC.
7. Waits to the PVC to bind to a persistent volume resource. twistcli expects that the persistent volume has already been created by the user. Note that the PVC is not deleted and recreated because once the PVC is be deleted, it cannot bind again to the persistent volume without recreating the persistent volume.
8. Retrieves the service IPs (Cluster IPs, and adds them to the SAN.
9. Creates a config map.
10. Resolves Console template to a file, and creates a Console replication controller.
11. Deletes the working directory.


---

# 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.prismacloud.io/admin-guide/tools/twistcli-console-install.md?ask=<question>&goal=<user_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.