Helm chart configMap volume mount prevents certificate persistence

critical

configurationUpdated Feb 7, 2022(via Exa)

Sources

Post-mortem: 1h30 downtime on a Saturday morning - DEV Communitydev.to

Technologies:

Traefiksubject

KubernetesKubernetes metrics correlate with this issue and help confirm diagnosis

How to detect:

ConfigMap volume explicitly mounted to /data path in Helm values conflicts with persistence configuration, causing PersistentVolume to be ignored and acme.json to be lost on every pod restart, triggering duplicate certificate requests

Recommended action:

Review Traefik Helm chart values.yaml for volumes array entries. Remove any volume with mountPath: /data and type: configMap. Ensure only persistence.enabled=true controls /data mount. Compare against working Traefik deployments or official Helm chart reference. After changes, verify PVC is created and bound to /data.