Connectware Agent Helm Chart

Deploy and configure multiple Connectware Agents using the connectware-agent Helm chart.

Use the connectware-agent Helm chart to orchestrate multiple Connectware Agents 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.

• 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.

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.

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

values.yaml

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

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

values.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

In this example:

• bender-robots and painting-robots inherit all defaults

• welder-robots overrides podPriorityClassName with a different value

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.