> 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-4-1/cybus-helm-charts/connectware-helm-chart.md).

# Connectware Helm Chart

The `connectware` Helm chart orchestrates Connectware on Kubernetes. As a complex application with a wide range of use cases, it offers a lot of configuration parameters that you may or may not need to get familiar with depending on your use case. It also includes the `connectware-agent` and `connectware-toolkit` Helm charts as optional subcharts.

We recommend getting familiar with it in a test environment before attempting a production deployment.

The `connectware` Helm chart is located at `oci://repo.cybus.io/charts/connectware`.

## Subcharts

The `connectware` Helm chart includes the following optional subcharts. Each has its own chapter that documents its configuration values, regardless of whether you install it as a subchart or as a standalone Helm installation:

* [connectware-agent Helm Chart](/2-4-1/cybus-helm-charts/connectware-agent-helm-chart.md) — Mass-orchestrates [Connectware Agents](/2-4-1/documentation/agents.md) using a defaults-and-overrides configuration model. Configure it under the `connectwareAgent` value of the `connectware` chart.
* [connectware-toolkit Helm Chart](/2-4-1/cybus-helm-charts/connectware-toolkit-helm-chart.md) — Deploys a `connectware-toolkit` container that ships with CLI tools for debugging Connectware on Kubernetes. Configure it under the `toolkit` value of the `connectware` chart.


---

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