Configuring Agent Persistence for the connectware-agent Helm Chart
Configure persistent storage for agents deployed with the connectware-agent Helm chart, including storage class, volume size, and access mode.
Last updated
Was this helpful?
Configure persistent storage for agents deployed with the connectware-agent Helm chart, including storage class, volume size, and access mode.
Agents deployed with the connectware-agent Helm chart use persistent storage to retain data across pod restarts and upgrades.
You can configure the storage class, volume size, and access mode to match your cluster's storage capabilities and performance requirements.
You cannot change persistence configuration for existing agents. To apply persistence changes, you must uninstall the agent and remove its PersistentVolumeClaim, then reinstall the agent with the new configuration.
By default, agents use the Kubernetes cluster's default storage class. To specify a different storage class, set the persistence.storageClassName parameter in your values.yaml file. Replace ${STORAGE_CLASS_NAME} with the name of your storage class.
protocolMapperAgentDefaults:
persistence:
storageClassName: ${STORAGE_CLASS_NAME}To see which storage classes are available in your cluster, run kubectl get sc.
If your cluster has no default storage class and you do not configure this parameter, the PersistentVolumeClaim remains unscheduled and the agent cannot start.
To override this setting for specific agents, set persistence.storageClassName within specific agent entries in protocolMapperAgents, as described in Configuration Principles for the connectware-agent Helm Chart.
To specify the size of the PersistentVolume used by agents, set the persistence.size parameter in your values.yaml file to a valid Kubernetes quantity:
protocolMapperAgentDefaults:
persistence:
size: 500MiTo specify the access mode for the PersistentVolume used by agents, set the persistence.accessMode parameter in your values.yaml file:
Valid values are ReadWriteOnce, ReadWriteMany, and ReadWriteOncePod.
Last updated
Was this helpful?
Was this helpful?
protocolMapperAgentDefaults:
persistence:
accessMode: ReadWriteMany
