Helm chart deployment fails when persistence is disabled

Issues
, , ,
1

Chart-Version: dgraph-0.0.13

Using the chart options to disable persistence for a test installation the statefulset.yaml of alpha and zero fail to render because of false indentation.

Used values.yml:

zero:
  persistence:
    enabled: false
    storageClass: "none"
    accessModes:
      - ReadWriteOnce
    size: 8Gi

alpha:
  persistence:
    enabled: false
    storageClass: "none"
    accessModes:
      - ReadWriteOnce
    size: 10Gi
    annotations: {}

Snippet of the wrong rendered yaml:

      volumes:
      - name: datadir
        persistentVolumeClaim:
          claimName: datadir
        - name: datadir
          emptyDir: {}

Check the indentation of the last two lines!

After resolving this the helm deployment is succesfull, but kubernets won’t render any pods.
Now we have two volumes with the name “datadir”

      volumes:
      - name: datadir
        persistentVolumeClaim:
          claimName: datadir
      - name: datadir
        emptyDir: {}

I resolved this by fetching the chart and deleting the lines in StateFulSet of alpha and zero which created the false volumes.

5

Hello.

Thank you so much for bringing this up. We will look into this.

Joaquin

7

This PR fixes the failed Helm installation when persistence is disabled:

https://github.com/dgraph-io/charts/pull/60

8

@a_kauerz This fix now available in dgraph-0.0.14:

1 Like