Uninstalling Connectware Agents with the connectware-agent Helm Chart

Remove agents deployed with the connectware-agent Helm chart.

Prerequisites

• Helm version 4 is installed on your system.

• kubectl is installed on your system.

• kubectl configured with the current context pointing to your target cluster (Configure Access to Multiple Clusters).

Uninstalling All Agents from One Installation

To remove all agents installed with the connectware-agent Helm chart, run the helm uninstall command followed by the name of your installation (also known as the release). You assigned this name yourself when deploying with the connectware-agent chart.

In the examples provided in this documentation, the release is called connectware-agent. If you’re unsure of the name you chose, you can look it up by running helm list for the namespace where you installed your agents.

Example

helm list -n ${NAMESPACE}

Replace ${NAMESPACE} with the namespace where you installed your agents.

NAME             	NAMESPACE         	REVISION	UPDATED                                	STATUS  	CHART                    	APP VERSION
connectware-agent	connectware-staging	1       	2026-04-08 14:49:49.29654165 +0200 CEST	deployed	connectware-agent-3.0.0 	2.3.0

Once you have determined the name of your installation, you can uninstall it.

Example

helm uninstall -n ${NAMESPACE} connectware-agent

This terminates running pods and removes their Kubernetes objects. However, PersistentVolumeClaims and their associated PersistentVolumes are retained. If you wish to clean them up, you can do so by using the label app.kubernetes.io/instance in combination with kubectl delete. The value for this label is the release name you already used to uninstall.

Example

kubectl delete -n ${NAMESPACE} pvc -l app.kubernetes.io/instance=connectware-agent

Uninstalling Single Agents from a Larger Installation

• To remove specific agents while keeping others, delete their entries from the protocolMapperAgents list in your values.yaml file and apply the changes with helm upgrade.

Example

1. To remove the agent welder-robots, delete its entry from the protocolMapperAgents list:

values.yaml

protocolMapperAgentDefaults:
  connectwareHost: connectware.cybus # adjust to actual hostname of Connectware
protocolMapperAgents:
  - name: bender-robots
    resources:
      limits:
        cpu: 2000m
        memory: 4000Mi
  #- name: welder-robots # welder-robots will be removed with helm upgrade
  #  resources:
  #    limits:
  #      cpu: 500m
  #      memory: 1000Mi
  - name: painter-robots
    resources:
      limits:
        cpu: 1000m
        memory: 2000Mi

1. Apply the changes:

helm upgrade connectware-agent oci://repo.cybus.io/charts/connectware-agent -f values.yaml -n ${NAMESPACE}

This deletes the pods and Kubernetes objects of the removed agents. PersistentVolumeClaims are retained and must be cleaned up manually.

1. List all available PersistentVolumeClaims to find the ones to delete:

kubectl get pvc -n ${NAMESPACE} -l app.kubernetes.io/component=protocol-mapper-agent

1. Delete the specific PersistentVolumeClaims associated with the removed agent. Replace data-connectware-agent-welder-robots-0 with the actual PVC name from the list above.

kubectl delete pvc -n ${NAMESPACE} data-connectware-agent-welder-robots-0