> 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-agent-helm-chart/kubernetes-object-names.md).

# Controlling Kubernetes Object Names for the connectware-agent Helm Chart

Customize the naming of Kubernetes objects created by 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 chart automatically removes the duplicate prefix. For example, a release named `connectware-agent` with an agent named `bender-robots` creates a StatefulSet named `connectware-agent-bender-robots` instead of `connectware-agent-connectware-agent-bender-robots`.

## Customizing Object Names

Customize the naming convention using two top-level Helm values:

| Value              | Description                                                                                  |
| ------------------ | -------------------------------------------------------------------------------------------- |
| `nameOverride`     | Overrides the chart name (second part of the prefix).                                        |
| `fullnameOverride` | Overrides the entire prefix (both release and chart name). Set to `""` to remove the prefix. |

Set both values at the top level of your `values.yaml` file, outside of `protocolMapperAgentDefaults` and `protocolMapperAgents`.

{% hint style="warning" %}
Changing the name of Kubernetes objects after deploying an agent orphans existing objects and creates new ones. Configure the naming convention before deploying agents.
{% endhint %}

### Using nameOverride

To replace the chart name portion of the prefix, set `nameOverride` in your `values.yaml` file. For an installation named `agents` with `nameOverride` set to `cw-agent`:

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

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

{% endcode %}

**Result:** StatefulSet named `agents-cw-agent-bender-robots`.

### Using fullnameOverride with a Custom Prefix

To replace the entire prefix with a custom string, set `fullnameOverride` in your `values.yaml` file. For an installation named `connectware-agents` with `fullnameOverride` set to `my-agents`:

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

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

{% endcode %}

**Result:** StatefulSet named `my-agents-bender-robots`.

### Using fullnameOverride to Remove the Prefix

To remove the prefix entirely so object names match the agent name, set `fullnameOverride` to an empty string in your `values.yaml` file. For an installation named `connectware-agents`:

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

```yaml
fullnameOverride: ''
protocolMapperAgents:
  - name: bender-robots
```

{% endcode %}

**Result:** StatefulSet named `bender-robots`.

## Reference

For the full list of Helm values, see the [Helm Chart Reference](/2-6-1/reference/helm-chart-reference.md#connectware-agent-helm-chart-values-reference).


---

# 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-agent-helm-chart/kubernetes-object-names.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.