Controlling the Name of Kubernetes Objects for the connectware-agent Helm Chart

By default, Kubernetes objects created by the connectware-agent Helm chart use a naming convention that combines the Helm release name and chart name as prefixes. This ensures unique, non-conflicting object names across your cluster.

Default Naming Convention

The default naming pattern is: <release-name>-<chart-name>-<agent-name>

When the release name and chart name are identical, the duplicate prefix is automatically removed. For example, if you follow the recommendations in this documentation and name your release connectware-agent, an agent named bender-robots creates a StatefulSet named connectware-agent-bender-robots instead of connectware-agent-connectware-agent-bender-robots.

Customizing Object Names

You can customize the naming convention using the following Helm values:

Value	Description
nameOverride	Overrides the chart name (second part of the prefix)
fullnameOverride	Overrides the entire prefix (both release and chart name)

Examples

The following examples demonstrate how to use these Helm values to control Kubernetes object names.

Using nameOverride

Setting nameOverride to cw-agent for an installation named agents:

nameOverride: cw-agent protocolMapperAgents: - name: bender-robots

Result: StatefulSet named agents-cw-agent-bender-robots

Using fullnameOverride with Custom Prefix

Setting fullnameOverride to my-agents for an installation named connectware-agents:

fullnameOverride: my-agents protocolMapperAgents: - name: bender-robots

Result: StatefulSet named my-agents-bender-robots

Using fullnameOverride to Remove Prefix

Setting fullnameOverride to an empty string for an installation named connectware-agents:

fullnameOverride: "" protocolMapperAgents: - name: bender-robots

Result: StatefulSet named bender-robots