> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/cybus-helm-charts/connectware-toolkit-helm-chart.md).

# Connectware Toolkit Helm Chart

Deploy a debugging toolkit container alongside Connectware using the connectware-toolkit Helm chart.

The `connectware-toolkit` chart deploys a `connectware-toolkit` container that ships with CLI tools for debugging Connectware on Kubernetes. These tools are stripped from Connectware images to reduce their security and file system footprint. The chart also includes custom tools written specifically for Connectware.

## Installation Options

You can install the chart using one of the following approaches:

* **As a subchart of the `connectware` chart:** Specify values in the `toolkit` section of the `connectware` chart. The toolkit is then deployed and managed as part of the Connectware installation.
* **As a separate Helm installation:** Install `connectware-toolkit` independently from Connectware. This lets you control the toolkit independently from your Connectware installation.

**`connectware-toolkit` Helm chart location:** `oci://repo.cybus.io/charts/connectware-toolkit`

## Configuration

The `connectware-toolkit` chart supports the same configuration values as the other Cybus Helm charts. See [Working with Cybus Helm Charts](/2-6-1/cybus-helm-charts/working-with-cybus-helm-charts.md) for more information on configuring these values.


---

# 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.cybus.io/2-6-1/cybus-helm-charts/connectware-toolkit-helm-chart.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.