Skip to content

configMapsHash

Feature state: 1.1.0

configMapsHash value in Kubedeploy enables custom annotation on Deployment and Statefulsets. Hash is automatically calculated based on the contents of deployed ConfigMaps.

Note

configMapsHash in Kubedeploy is disabled by default.

enabling this feature will trigger Pod rolling restarts whenever content of configMaps data or name is changed. This can be useful if the application can't detect any mounted ConfigMap file content changes.

Enable configMapsHash

values.yaml
nameOverride: my-app
image:
  repository: nginx
  tag: latest

configMaps:
  - name: configmap1
    mount: True # (optional) Should this configmap be mounted as volume in containers?
    mountPath: /data/confmap # (required if mount=True) Define mount path for this configmap
    data:
      kubedeploy.txt: |+
        configmap values

  - name: configmap2
    data:
      config: |+
        config2

configMapsHash: true
Deploy command
helm install webapp sysbee/kubedeploy -f values.yaml

See also: