> 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-agent-helm-chart.md).

# Connectware Agent Helm Chart

Use the `connectware-agent` Helm chart to orchestrate multiple [Connectware Agents](/2-4-1/documentation/agents.md) with a defaults-and-overrides configuration model. You define default settings that apply to all agents, then override specific parameters for specific agents as needed (for example, agent name or resource limits).

## Installation Options

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

* **As a subchart of the `connectware` chart:** Specify values in the `connectwareAgent` section of the `connectware` chart. See [Installing Connectware Agents Using the connectware-agent Helm Chart](/2-4-1/documentation/agents/agents-in-kubernetes/installing-connectware-agents-using-the-connectware-agent-helm-chart.md).
* **As a separate Helm installation:** Install `connectware-agent` independently from Connectware. This provides deployment flexibility, as you can upgrade agents separately from the main Connectware installation. See [Deploying Agents with Your Connectware Installation](/2-4-1/documentation/agents/agents-in-kubernetes/deploying-agents-with-your-connectware-installation.md).

You can further separate agents into multiple `connectware-agent` installations based on logical grouping (for example, by factory zone or machine type) to maintain independent upgrade cycles.

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

For an overview of all available configuration options for the `connectware-agent` Helm chart, see the [Helm Chart Reference](/2-4-1/reference/helm-chart-reference.md#connectware-agent-helm-chart-values-reference).

## Configuration Principles for the connectware-agent Helm Chart

The chart uses a two-level configuration structure:

1. **Agent defaults** (`protocolMapperAgentDefaults`) — settings that apply to all agents
2. **Per-agent overrides** (`protocolMapperAgents`) — agent-specific configuration

This approach simplifies management when deploying many similar agents while retaining flexibility for agent-specific requirements.

### Defining Agent Defaults

Use `protocolMapperAgentDefaults` to define settings that apply to all agents:

**Example: Agent defaults**

{% code title="values.yaml" lineNumbers="true" %}

```yaml
protocolMapperAgentDefaults:
  connectwareHost: connectware.cybus
  podPriorityClassName: high-priority
  tls:
    ca:
      existingConfigMap: connectware-ca-chain
```

{% endcode %}

All settings in `protocolMapperAgentDefaults` apply to every agent unless explicitly overridden on a per-agent basis.

### Configuring Specific Agents

The `protocolMapperAgents` section contains a list of agents, each describing a single protocol-mapper agent. Each agent requires a `name` value. All other settings inherit from `protocolMapperAgentDefaults` or use chart defaults.

To override an agent default for a specific agent, set the parameter within that agent's `protocolMapperAgents` configuration.

**Example: Per-agent configuration**

{% code title="values.yaml" lineNumbers="true" %}

```yaml
protocolMapperAgentDefaults:
  connectwareHost: connectware.cybus
  podPriorityClassName: high-priority
protocolMapperAgents:
  - name: bender-robots
  - name: welder-robots
    # unlike the other agents, this agent does not use the high-priority Pod PriorityClass
    podPriorityClassName: medium-priority
  - name: painting-robots
```

{% endcode %}

In this example:

* `bender-robots` and `painting-robots` inherit all defaults
* `welder-robots` overrides `podPriorityClassName` with a different value

{% hint style="info" %}
This configuration model works well when agents share common settings. For agents with significantly different configurations, consider creating separate Helm releases (installations) of the `connectware-agent` chart to maintain a clear separation and independent deployment control.
{% endhint %}


---

# 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-agent-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.